Post-History should include dates of postings to python-ideas by phdru · Pull Request #441 · python/peps
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?
| * 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> |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should now say dates of postings to python-ideas and/or python-dev.
| 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. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also now say posted to python-ideas and/or python-dev.
| 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> |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment below.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
phdru
deleted the
pep1-posthistory
branch
This file contains hidden or 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