On Wed, Dec 14, 2011 at 5:05 PM, Thomas Dziedzic <gostrc@gmail.com> wrote:
On Wed, Dec 14, 2011 at 5:00 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 14.12.2011 23:24, schrieb Evan Martin:
What I don't understand is why you're manually patching upstream software to rewrite references from /usr/bin/python to /usr/bin/python2. This sort of forking is exactly the sort of divergence (like how Ubuntu modified their GTK to add their own specific hooks) that I was fleeing from when I came to Arch.
There's no forking here. Python 2 is end-of-life, python 3 is current. Applications that set a 'python' shebang, but require 'python2' are *broken*, we *fix* them.
This is how I feel about the current situation also.
The pep clearly defines that you should only be using python2 or python3 in your shebangs, and that python should be ideally used only to invoke interactive sessions.
The fact that programmers and distro python packagers ignore this is not our fault.
"Until the conventions described in this PEP are more widely adopted, having python invoke python2 will remain the recommended option."