-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Convert PEPs 261, 267, 325, 358, 361 #204
Conversation
======== | ||
|
||
Character | ||
Used by itself, means the addressable units of a Python |
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.
How does this indented stuff look rendered? Should these be unindented and made into sub-sections?
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.
This becomes a definition list
item: http://cpython-devguide.readthedocs.io/documenting.html?highlight=definition%20list#lists-and-quotes
But I can convert these into sub-headings too.
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.
That looks reasonable to me!
LGTM |
pep-0261.txt
Outdated
represented as a single Python character. It generates two | ||
Python characters known as a "surrogate pair". Should this | ||
be disallowed on future narrow Python builds? | ||
Python currently allows \U literals that cannot be |
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.
Just noticed that the \U
isn't rendered correctly 😅
Will make another commit.
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.
Still LGTM 😄
Continuation for #4