#27878 closed Bug (invalid)
Move to Python 3 shebangs
| Reported by: | Chris Lamb | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Now that master branch is Python 3 only, we should use Python 3 shebangs. I just ran runtests.py and it used Python 2.. :)
Change History (8)
comment:1 by , 7 years ago
comment:3 by , 7 years ago
| Component: | Uncategorized → Core (Other) |
|---|
I found that the Windows installation of Python 3.x does not have an executable called python3, so I'm not sure if we should keep this change.
$ ./tests/runtests.py settings_tests /usr/bin/env: ‘python3’: No such file or directory
comment:4 by , 7 years ago
I remember about discussions on this issue. Different systems/distributions have different strategies around using python, python2 or python3.
I would tend to think that the environment in which you are running your Python scripts should point python to the right version. So +1 for reverting.
comment:6 by , 7 years ago
| Resolution: | fixed → invalid |
|---|
comment:7 by , 7 years ago
the environment in which you are running your Python scripts should point python to the right version
Hm, except for legacy reasons it is not really possible to change (eg. all Debian-derived distributions).
comment:8 by , 7 years ago
pyenv helps -- it's the most convenient solution I know for running a modern Python on Debian.
PR