Unify format & syntax across Python tutorial #379
Merged
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
Parts of these tutorials were indented with tabs, and others with 4 spaces. This conforms them all to 4 spaces.
One of my students last night got confused with the tutorial where we weren't directly calling `print()` and yet stuff was appearing on the screen. She wasn't sure if simply typing out the variable was somehow *doing* something. Using `print()` explicitly everywhere should clear this up. Similarly, `>>> ` was only being used in parts of the document, leaving it unclear as to whether this is something that needs to be typed, or if perhaps the absence of it meant they weren't in the REPL. This commit addressed both issues.
I think this is probably clearer and more grammatically correct.
KimberleyCook
approved these changes
Jan 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There were a number of inconsistencies in how the tutorial presents code, most commonly with using
>>>sometimes and regularly just typing out the variable name to mean "let the REPL tell you what this means" rather than usingprint(variable_name). This PR fixes both of those, along with some general clean up.