[Python-porting] Shebang lines for Python 3
asmeurer at gmail.com
Mon Sep 5 21:22:21 CEST 2011
OK, so actually Arch was the counterexample given in the other
discussion too. Does Arch not include a python3 alias? Is it safe to
say that Arch was really stupid for doing this, as it will break every
single Python 2 script that someone wants to use, so that we can just
And can someone point to relevant distutils documentation on how to do
this? I don't think that Vladimir's actually set up our setup.py
script yet to handle our Python 3 work.
On Mon, Sep 5, 2011 at 4:10 AM, Lennart Regebro <regebro at gmail.com> wrote:
> On Mon, Sep 5, 2011 at 11:42, Vladimir Perić <vlada.peric at gmail.com> wrote:
>> On Mon, Sep 5, 2011 at 9:54 AM, Eike Hein <hein at kde.org> wrote:
>> > On 9/4/2011 9:07 PM, Aaron Meurer wrote:
>> >> This shortcut works on my machine, but I don't know if it's universal
>> >> to all Python 3 installs. This certainly would make it easier to me
>> >> developing with those scripts, because I can just call ./script.py,
>> >> but I'm wondering if it's proper to use that in the final (Python 3
>> >> version of the) release of the package.
>> > I remember reading somewhere that it's currently the
>> > recommendation of Python upstream to leave "python"
>> > at Python 2.x - possibly even indefinitely - and use
>> > "python3" for Python 3. Arch went against the grain
>> > there, it seems.
>> If that's the case, would it make sense to have 2to3 automatically
>> convert these shebang lines? As a separate (perhaps not enabled by
>> default) fixer maybe?
> That's not possible as you don't know what they should be. And in any case,
> the installer should adjust them (as distutils does, for example).
> Python-porting mailing list
> Python-porting at python.org
More information about the Python-porting