* Update pep-0008.txt
Clarified contradictions regarding comment formatting. NB Complete sentences should have a period.
* Update pep-0008.txt
Changed to remove reference to short comments without terminating period.
* Update pep-0008.txt
Further refined, corrected incorrect, fixed singular/plural.
* Update pep-0008.txt
* Update pep-0008.txt
Edit for consistency use 'multi-' in 'multi-line` 'multi-statement` 'multi-sentence` etc with dash rather than space or no splitter (eg 'multi line`, 'multiline`). If a different convention is preferred, do that.
* Update pep-0008.txt 'latin' capitalization
'Latin' is a proper noun, and thus should be capitalized.
* Update pep-0008.txt 'boolean' capitalization
Capitalization should be consisted. I propose 'boolean' should always be capitalized, as per https://english.stackexchange.com/questions/4481/should-the-word-boolean-be-capitalized
At present it is inconsistently capitalised.
Changed 'boolean' to 'Boolean'
* Update pep-0008.txt - 'unicode' capitalization
Update pep-0008.txt - as a proper noun, 'unicode' should be capitalized. Fixed 3 instances.
* Revise Update pep-0008.txt
Removed revisions to 'boolean', 'unicode'.
Unicode capitalization [issue](https://bugs.python.org/issue31873) under discussion.
* Removed trailing newlines
Removed trailing newlines
* Standardised 'multiline', reworded 'Latin'
Made the form 'multiline' uniform throughout the document.
Clarified references to Latin alphabet to direct to the specific character set desired.
* Removed errant period
* Moved 'alphabet'
Moved 'alphabet' before encoding parenthesis line 336.
It turns out that *any* write-back based design has
inherent flaws that make it difficult to build a source
debugger that reliably allows mutation of function local
variables.
So this switches to Nathaniel's suggested write-through
proxy idea, but constrains it to only applying when a
trace hook is installed. This means the official language
level semantics can just use the simpler model where
rebinding function local variables via locals() simply
isn't possible - only folks already working with frames
and trace functions will need to be aware of the semantics
of the write-through proxy.
* Add "Issues caused by precision loss" section with two examples
* Alternatives: add new "Modify time.time() result type" and
"New time_ns module" sections
Berker Peksag
Gerrit Holl
Ben Hoyt
toonarmycaptain
Ethan Smith
Victor Stinner
Christopher H.Barker, PhD
Jakub Wilk
Lukasz Langa
Oleg Broytman
Brett Cannon
Lilian Besson
Huang Huang
Masayuki Yamamoto
Guido van Rossum
Antoine Pitrou
Nick Coghlan
Ned Deily
wangqr
Barry Warsaw
Benjamin Peterson
Ioannis Filippidis
Eric Snow