Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork34k
Clarify wording in tutorial examples#144360
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
Hamza-CS50 wants to merge1 commit intopython:mainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Open
+1 −1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This change slightly clarifies wording in the tutorial to make it easier for beginners to understand which parts of the examples they should type into the interpreter.
python-cla-botbot commentedJan 31, 2026 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
All commit authors signed the Contributor License Agreement. |
| In the following examples, input and output are distinguished by the presence or | ||
| absence of prompts (:term:`>>>` and:term:`...`): to repeat the example, you must type | ||
| everything after the prompt, when the prompt appears; lines that do not begin | ||
| everythingshownafter the prompt, when the prompt appears; lines that do not begin |
Member
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 how this helps, it doesn’t clarify much, to me this seems like churn.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
awaiting reviewdocsDocumentation in the Doc dir pendingThe issue will be closed if no feedback is provided skip issueskip news
2 participants
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.
Uh oh!
There was an error while loading.Please reload this page.
This change slightly clarifies wording in the tutorial to make it easier for beginners to understand which parts of the examples they should type into the interpreter.
📚 Documentation preview 📚:https://cpython-previews--144360.org.readthedocs.build/