Post-History should include dates of postings to python-ideas #441
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We had a discussion on python-dev about this (buried in the PEP 517 thread), and Guido expressed the opinion of dropping python-list and adding python-ideas. I agree with that, although it's a process change and will require notification to the relevant mailing lists. Can you please make that change to this PR? |
warsaw
requested changes
Oct 27, 2017
pep-0001.txt
Outdated
| @@ -379,7 +379,8 @@ optional and are described below. All other headers are required. :: | |||
| * Requires: <pep numbers> | |||
| Created: <date created on, in dd-mmm-yyyy format> | |||
| * Python-Version: <version number> | |||
| Post-History: <dates of postings to python-list and python-dev> | |||
| Post-History: <dates of postings to python-list, python-dev | |||
| and/or python-ideas> | |||
There was a problem hiding this comment.
This should now say dates of postings to python-ideas and/or python-dev.
pep-0001.txt
Outdated
| headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2001. | ||
| versions of the PEP are posted to python-list, python-dev and/or | ||
| python-ideas. Both headers should be in dd-mmm-yyyy format, e.g. | ||
| 14-Aug-2001. |
There was a problem hiding this comment.
This should also now say posted to python-ideas and/or python-dev.
phdru
force-pushed
the
pep1-posthistory
branch
from
9f1c87c
to
119801c
Compare
|
@warsaw Done. |
warsaw
reviewed
Oct 27, 2017
pep-0001.txt
Outdated
| @@ -379,7 +379,7 @@ optional and are described below. All other headers are required. :: | |||
| * Requires: <pep numbers> | |||
| Created: <date created on, in dd-mmm-yyyy format> | |||
| * Python-Version: <version number> | |||
| Post-History: <dates of postings to python-list and python-dev> | |||
| Post-History: <dates of postings to python-dev and/or python-ideas> | |||
There was a problem hiding this comment.
Actually, this needs to be python-ideas and/or python-dev. The reasoning is that python-dev must always be included but python-ideas is optional.
phdru
force-pushed
the
pep1-posthistory
branch
from
119801c
to
45f291e
Compare
|
@warsaw Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs: https://mail.python.org/pipermail/python-dev/2017-October/149990.html