iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minor clarification for PEP 512

This commit is contained in:
Brett Cannon 2016-01-19 12:17:28 -08:00
parent ee38420e88
commit 5a91baba5d
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0007.txt
View File

@ -75,9 +75,9 @@ Code lay-out
} }
* Code structure: one space between keywords like ``if``, ``for`` and * Code structure: one space between keywords like ``if``, ``for`` and
the following left paren; no spaces inside the paren; braces may be the following left paren; no spaces inside the paren; braces are
omitted where C permits but when present, they should be formatted strongly preferred but may be omitted where C permits, and they
as shown:: should be formatted as shown::
if (mro != NULL) { if (mro != NULL) {
... ...

4
pep-0512.txt
View File

@ -233,7 +233,9 @@ be chosen which gives us a linear history by using Git's CLI. The
expectation is that all pull requests will be fast-forwarded and expectation is that all pull requests will be fast-forwarded and
rebased before being pushed to the master repository. This should rebased before being pushed to the master repository. This should
give proper attribution to the pull request author in the Git give proper attribution to the pull request author in the Git
history. history. This does have the consequence of losing some GitHub
features such as automatic closing of pull requests, link generation,
etc.
A second set of recommended commands will also be written for A second set of recommended commands will also be written for
committing a contribution from a patch file uploaded to committing a contribution from a patch file uploaded to