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

Fix some small typos in PEP 512 (#287)

This commit is contained in:
csabella 2017-06-07 17:37:59 -04:00 committed by Brett Cannon
parent 8350530c12
commit b85afac44d
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0512.txt
View File

@ -60,7 +60,7 @@ languishing on the issue tracker due to core developers not being
able to work through the backlog fast enough to keep up with able to work through the backlog fast enough to keep up with
submissions. In turn, that led to a side-effect issue of discouraging submissions. In turn, that led to a side-effect issue of discouraging
outside contribution due to frustration from lack of attention, which outside contribution due to frustration from lack of attention, which
is dangerous problem for an open source project with no corporate is a dangerous problem for an open source project with no corporate
backing as it runs counter to having a viable future for the project. backing as it runs counter to having a viable future for the project.
While allowing patches to be uploaded to bugs.python.org [#b.p.o]_ is While allowing patches to be uploaded to bugs.python.org [#b.p.o]_ is
potentially simple for an external contributor, it is as slow and potentially simple for an external contributor, it is as slow and
@ -314,7 +314,7 @@ tracker).
The association between a pull request and an issue will be done based The association between a pull request and an issue will be done based
on detecting an issue number. If the issue is specified in either the on detecting an issue number. If the issue is specified in either the
title or in the body of a message on a pull request then connection title or in the body of a message on a pull request then a connection
will be made on bugs.python.org [#b.p.o]_. Some visible notification will be made on bugs.python.org [#b.p.o]_. Some visible notification
-- e.g. label or message -- will be made to the pull request to -- e.g. label or message -- will be made to the pull request to
notify that the association was successfully made. notify that the association was successfully made.
@ -401,7 +401,7 @@ modernization, working with the ``Misc/NEWS`` file will be
simplified. simplified.
The planned approach is to use an individual file per news entry, The planned approach is to use an individual file per news entry,
containing the text for the entry. In this scenario each feature containing the text for the entry. In this scenario, each feature
release would have its own directory for news entries and a separate release would have its own directory for news entries and a separate
file would be created in that directory that was either named after file would be created in that directory that was either named after
the issue it closed or a timestamp value (which prevents collisions). the issue it closed or a timestamp value (which prevents collisions).
@ -520,7 +520,7 @@ re-run the tests in case of test flakiness will be needed, whether it
is from removing a "test failed" label, web interface for core is from removing a "test failed" label, web interface for core
developers to trigger another testing event, etc. developers to trigger another testing event, etc.
Inspiration or basis of the bot could be taken from pre-existig bots Inspiration or basis of the bot could be taken from pre-existing bots
such as Homu [#homu]_ or Zuul [#zuul]_. such as Homu [#homu]_ or Zuul [#zuul]_.
The name given to this bot in order to give it commands is an open The name given to this bot in order to give it commands is an open