-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
PEP 394: Allow for more flexibility in handling /usr/bin/python #989
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
Changes from 1 commit
68475c0
abf3bf3
4a4cdf7
36e61fa
268e96d
5e439bd
2e763f3
627ae44
4af8f14
8d88ea0
9546b15
fee50a4
4b20f8c
cca28c0
5d3e9d8
6dbfc2f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -236,10 +236,14 @@ 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. | ||
| * When 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 | ||
| is released. | ||
| * Even as the Python 2 interpreter becomes less common, scripts should | ||
| nevertheless continue to use the ``python3`` convention rather than just | ||
| ``python``. In the event of a future Python 4.0 release, distributors may | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd suggest leaving out any mention of Python 4. 1) it can create FUD; 2) it's entirely vaporware; 3) we don't even know whether there will be a Python 4 or what it will look like. We can always add a Python 4 recommendation when the time comes.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agreed. Good catch @warsaw |
||
| then choose to simply alias ``python3`` to the same binary as ``python4`` | ||
| (if the degree of change will be the same as in any other Python feature | ||
| release), or else they may choose to maintain parallel ``python3`` and | ||
| ``python4`` stacks for a time (depending on the needs of their specific | ||
| audience). | ||
| * If these conventions are adhered to, it will become the case that the | ||
| ``python`` command is only executed in an interactive manner as a user | ||
| convenience, or else when using a virtual environment or similar mechanism. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.