Acceptance of PEPs
I just found out that PEP 430 came up again and was approved, but only because of another website. After that I looked back through my email only to find mention via python-checkins. Aren't PEPs typically acted on here on python-dev? I mention this because I was writing up a blog.python.org post about the (somewhat recent) Sphinx theme change and the change to add a version dropdown which was pushed yesterday. I was about to wrap it up and schedule it for tomorrow when I found out about 430, which I'm now including. note: I have no problems with that PEP actually being approved. I've wanted that change for 2 years.
On Sun, Oct 28, 2012 at 9:05 PM, Brian Curtin <brian@python.org> wrote:
I just found out that PEP 430 came up again and was approved, but only because of another website. After that I looked back through my email only to find mention via python-checkins. Aren't PEPs typically acted on here on python-dev?
FWIW, the following e-mail was cross-posted to python-dev: http://mail.python.org/pipermail/python-ideas/2012-October/017494.html The message doesn't seem to show up in the python-dev archives though: http://mail.python.org/pipermail/python-dev/2012-October/thread.html Perhaps this is because python-dev was the "CC" rather than the "To" (which was python-ideas). Here is another message that does show up in the python-dev archives (and which quotes the acceptance): http://mail.python.org/pipermail/python-dev/2012-October/122458.html --Chris
Am 29.10.2012 05:05, schrieb Brian Curtin:
I just found out that PEP 430 came up again and was approved, but only because of another website. After that I looked back through my email only to find mention via python-checkins. Aren't PEPs typically acted on here on python-dev?
Yes, that's why I cross-posted the acceptance email here.
I mention this because I was writing up a blog.python.org post about the (somewhat recent) Sphinx theme change and the change to add a version dropdown which was pushed yesterday. I was about to wrap it up and schedule it for tomorrow when I found out about 430, which I'm now including.
note: I have no problems with that PEP actually being approved. I've wanted that change for 2 years.
For most PEPs, a longer contemplation and discussion period is of course required. But in this case I don't think a PEP would have been required anyway, and it matched more or less what was already discussed this time *and* the last time this came up (at which time I didn't act on it). So it seemed the best course of action to do it right now. Georg
On Oct 28, 2012, at 11:05 PM, Brian Curtin wrote:
I just found out that PEP 430 came up again and was approved, but only because of another website. After that I looked back through my email only to find mention via python-checkins. Aren't PEPs typically acted on here on python-dev?
I mention this because I was writing up a blog.python.org post about the (somewhat recent) Sphinx theme change and the change to add a version dropdown which was pushed yesterday. I was about to wrap it up and schedule it for tomorrow when I found out about 430, which I'm now including.
PEP 1 states that proposals must be sent to python-dev after discussion on python-ideas. As for acceptance, PEP 1 says: Once the authors have completed a PEP, they may request a review for style and consistency from the PEP editors. However, the content and final acceptance of the PEP must be requested of the BDFL, usually via an email to the python-dev mailing list. ... When a PEP is Accepted, Rejected or Withdrawn, the PEP should be updated accordingly. In addition to updating the status field, at the very least the Resolution header should be added with a link to the relevant post in the python-dev mailing list archives. So yes, python-dev needs to be the place where PEPs are discussed and accepted. Cheers, -Barry
participants (4)
-
Barry Warsaw -
Brian Curtin -
Chris Jerdonek -
Georg Brandl