You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got this error when adding bin/vsc_env.py to vsc-config:
test_importscripts (vsc.install.commontest.CommonTest)
Try to import each python script as a module ... INFO: run_tests from base dir /Users/kehoste/work/vsc-config (using executable /Users/kehoste/work/vsc-config/setup.py)
INFO: generated list: ['bin/vsc_env.py']
INFO: generated scripts list: ['bin/vsc_env.py']
INFO: get_header for script
INFO: python in shebang, forcing env python (header modified)
INFO: run_tests from base dir /Users/kehoste/work/vsc-config (using executable /Users/kehoste/work/vsc-config/setup.py)
INFO: found match url [email protected]:hpcugent/vsc-config in /Users/kehoste/work/vsc-config/.git/config
INFO: found match name vsc-config in /Users/kehoste/work/vsc-config/.git/config
INFO: reg found: ('github.com', 'hpcugent/vsc-config')
INFO: get_name_url returns {'url': 'https://github.com/hpcugent/vsc-config', 'name': 'vsc-config', 'download_url': 'https://github.com/hpcugent/vsc-config/archive/ALL_VERSIONS.tar.gz'}
INFO: found license /Users/kehoste/work/vsc-config/LICENSE with md5sum 4c917d76bb092659fa923f457c72d033
INFO: Found license name ARR and classifier License :: Other/Proprietary License
FAIL
The FAIL doesn't give any hint on what is wrong exactly, in the end it turned out that the problem was that /usr/bin/python was being used as shebang line rather than /usr/bin/env python, which is signalled by the python in shebang line above.
Problems like this should stand out better so you don't have to be a detective to figure out what the actual problem is.
The text was updated successfully, but these errors were encountered:
I got this error when adding
bin/vsc_env.py
tovsc-config
:The
FAIL
doesn't give any hint on what is wrong exactly, in the end it turned out that the problem was that/usr/bin/python
was being used as shebang line rather than/usr/bin/env python
, which is signalled by thepython in shebang
line above.Problems like this should stand out better so you don't have to be a detective to figure out what the actual problem is.
The text was updated successfully, but these errors were encountered: