iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Drop a suggestion from PEP 394's migration notes that's a really bad idea in a world containing scripts that are source compatible with both Python 2 and 3

This commit is contained in:
Nick Coghlan 2012-02-16 21:46:35 +10:00
parent 2819d48c7b
commit debf680236
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0394.txt
View File

@ -124,10 +124,6 @@ making such a change.
versa. That way, if a sysadmin does decide to replace the installed
``python`` file, they can do so without inadvertently deleting the
previously installed binary.
* As an alternative to the recommendation presented above, some distributions
may choose to leave the ``python`` command itself undefined, leaving
sysadmins and users with the responsibility to choose their own preferred
version to be made available as the ``python`` command.
* If the Python 2 interpreter becomes uncommon, scripts should nevertheless
continue to use the ``python3`` convention rather that just ``python``. This
will ease transition in the event that yet another major version of Python