> Providing
> an unversioned "python" serves only to lure incautious programmers into
> using it where they should use a versioned name.
My aim is for folks to start thinking of a "/usr/bin/python" shebang
as being akin to writing "/bin/sh" instead of "/bin/bash": as the
author of the script, by deciding not to explicitly qualify your
shebang line you're saying "I'm not writing in either Python 2 *or*
Python 3, I'm writing in the hybrid subset of both of them". There
aren't many good reasons for a script in a distro package to do that
(they should just depend on the stack they want), but there are plenty
of good reasons for multi-distro scripts to be written that way.
As time goes by, I'd expect the meaning of the unqualified variant to
shift slightly such that "/usr/bin/python" is taken to mean "written
in the oldest Python dialect that is still actively supported by
upstream and/or commercial vendors (or potentially even older than
that)" while "/usr/bin/python3" retains its current meaning of "run in
the default Python 3 stack" (with the two links thus becoming
functionally equivalent for systems that only have one Python stack
installed).
Cheers,
Nick.
--
Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org