GeezerVison is showing github.com — gh-100972: For command line examples in the documentation, use "python" rather than "python3" by furkanonder · Pull Request #100973 · python/cpython
Conversation
furkanonder
commented
Jan 12, 2023
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
furkanonder
changed the title
gh-100972: Prefer "python" over "python3"
gh-100972: For command line examples in the documentation, use "python" rather than "python3
Jan 12, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
|
|
|
|
* Python now gets the absolute path of the script filename specified on
|
|
|
the command line (ex: ``python3 script.py``): the ``__file__`` attribute of
|
|
|
the command line (ex: ``python script.py``): the ``__file__`` attribute of
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see much value in changing old release notes.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
hauntsaninja and erlend-aasland reacted with thumbs up emoji
|
Doesn't this assume that the system Python installation will be Python 3.x such that "python" will start a 3.x interpreter? If that's the case, it shouldn't be needed to specify "python3" for "-m venv" usages, right? Also, is it definitely the case that "python" will invoke 3.x on all platforms, old and new? For example I have some (not very) old Ubuntu machines where "python3" is needed. Anyone following along the documentation with this change could run into problems.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.
|
MonadChains reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.
If there are problems with the Mac, I think this PR should be reverted.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
hugovk
changed the title
gh-100972: For command line examples in the documentation, use "python" rather than "python3
gh-100972: For command line examples in the documentation, use "python" rather than "python3"
Apr 7, 2023
On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.
If there are problems with the Mac, I think this PR should be reverted.
I disagree; reverting that PR will only create more churn (both in the git history, but more importantly also by burning CI and contributor time). I'm closing this and the linked issue:
- There is no uncontroversial way to fix this
- Many core devs will categorise spelling fixes (including this) as churn; even more so given there is no consensus
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|