-
PEP 8: minor grammar improvement (#926)
From > does not import objects whose name starts with an underscore. into > does not import objects whose names start with an underscore. Closes python/pythondotorg#1387
-
PEP 0008: Clarify self-contradictory =-spacing rules (#820)
Previously, the PEP contained roughly the following three rules, in sequence: 1. Never use spaces around `=` when used to indicate a parameter default 2. Something unrelated 3. DO use spaces around `=` when used to indicate a parameter default if there is also a parameter annotation present This commit attempts to clarify this part of the PEP by: * Combining the first and third rules listed above into a single rule that addresses both annotated and unannotated parameters * Rephrasing the first rule to indicate that it applies only to unannotated parameters, to eliminate the logical contradiction
-
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
-
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
-
* 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.
-
Update pep-0008.txt Clarified contradictions regarding comment formatting. NB Complete sentences should have a period.
-
Cross-reference PEP 3131 from PEP 8 (#286)
PEP 3131 (Unicode identifiers) includes a policy section covering their use within the standard library. This adds an explicit cross-reference to that section from the prescriptive naming conventions section of PEP 8.
-
[WIP] Semantics of variance in type variables and notation conventions (
#68) * Semantics of variance in type variables and notation conventions * Notation convention for type variables in PEP 8
-
Fix various typos, spelling and grammar errors
intgr committedJul 11, 2016 Errors detected using Topy (https://github.com/intgr/topy), all changes verified by hand.
-
Clarify backward-compatible type annotations
Previous wording used the term "function annotations" which is overly generic. This commit modifies the wording to make it clear we don't mean arbitrary function annotations.
-
warsaw committed
Jun 8, 2016
-
warsaw committed
Jun 7, 2016 Put all module level dunders together in the same location, and remove the redundant version bookkeeping information. Closes #27187. Patch by Ian Lee.
-
Issue #27191: Improve markup of PEP 8, patch by Ian Lee
berkerpeksag committedJun 3, 2016
-
Backed out changeset: c4aef26d128b
serhiy-storchaka committedMay 3, 2016 Unknown interpreted text role "kbd".
-
serhiy-storchaka committed
May 3, 2016
-
PEP-8 Update on Knuth style breaking of a long formula. #issue26780
orsenthil committedApr 20, 2016 Patch by Brandon Rhodes provides clarity and rationale for this suggestion. Also fixes the example to use "+", "-" operators which have same precedence level. Reviewed by Guido van Rossum.
-
Rosuav committed
Apr 15, 2016 -
Fix typo. Revert my previous diff that removed another example breaki…
gvanrossum committedApr 15, 2016 …ng before "and".
-
According to Knuth, it is better to break *before* a binary operator.
gvanrossum committedApr 15, 2016
-
Fix style inconsistency with "and" on continuation line.
gvanrossum committedApr 14, 2016
-
Just refer to the spec in PEP 484 for straddling annotations instead …
gvanrossum committedMar 21, 2016 …of repeating the info in PEP 8.
-
Gramatical and other improvements given by thefourtheye.
warsaw committedFeb 22, 2016 Closes #26408
-
Clarify that stdlib experiments with annotations are not encouraged.
gvanrossum committedJan 5, 2016