-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3 as default python #4950
Comments
I assume you mean the binary name? There is a new discussion upstream https://mail.python.org/pipermail/python-dev/2019-February/156272.html for changing PEP 394 |
Yes |
cd bin; cp python3.exe python.exe ? |
That's my point. For reference, here is part of the upstream discussion on this. |
Once we get rid of python2 (#4993) we can switch python.exe over to python3, imo. |
python/peps#989 -> python can now point to python3
|
This moves pip.exe from python2-pip to python3-pip and makes it the Python 3 version. See msys2#4950
#5640 moves pip.exe |
I suggest that Python 3 be made the default python target in Msys2.
Python 2 End of Life is about 10 months from now.
Arch Linux can be used as a reference for this, as they have had python3 as default for quite some time now.
Edit:
To clarify, I think
/mingw64/bin/python --version
should returnpython 3.7.2
(or whatever latest version).Instead,
/mingw64/bin/python --version
returnspython 2.7.15
I understand this was done to preserve compatibility with legacy python programs. IMO it is a backwards way of doing things. I think this not just for python, but for any program:
foo
should execute the latest installed version, and older versions should be installed asfooX.Y
.One way this change could be made is to add a statement in the
prepare()
of every python2 PKGBUILD, to patch the shebang to target python2 explicitly.The text was updated successfully, but these errors were encountered: