[issue23077] PEP 1: Allow Provisional status for PEPs

2019-02-15 Thread Cheryl Sabella
Cheryl Sabella added the comment: Closing as third party since this moved to the PEP repository. -- resolution: -> third party stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue23077] PEP 1: Allow Provisional status for PEPs

2018-02-21 Thread Nick Coghlan
Nick Coghlan added the comment: I'll also note that I made my comments above about writing a new PEP prior to the migration to GitHub and the availability of a PR-based workflow for reviewing PEP changes. So consider the PR Cheryl linked and the post at

[issue23077] PEP 1: Allow Provisional status for PEPs

2018-02-21 Thread Cheryl Sabella
Cheryl Sabella added the comment: Pull request: https://github.com/python/peps/pull/577 -- nosy: +csabella ___ Python tracker ___

[issue23077] PEP 1: Allow Provisional status for PEPs

2014-12-31 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Dec 31, 2014, at 01:54 AM, Nick Coghlan wrote: As we've started working through the post-release PEP 440 changes, I think this is definitely worthy of a separate PEP. I'm open to discussion and ideas, but I want to caution against spreading information

[issue23077] PEP 1: Allow Provisional status for PEPs

2014-12-31 Thread Nick Coghlan
Nick Coghlan added the comment: The new PEP wouldn't be a permanent one - it would be describing the proposed changes to PEP 1, and the rationale for them. It would be for my own benefit as much as anyone's - if I can't explain the proposed change and its intended benefits clearly in PEP

[issue23077] PEP 1: Allow Provisional status for PEPs

2014-12-30 Thread Nick Coghlan
Nick Coghlan added the comment: As we've started working through the post-release PEP 440 changes, I think this is definitely worthy of a separate PEP. I'll take the opportunity to pitch some other changes as well, like separating out the interoperability standards from the informational PEPs

[issue23077] PEP 1: Allow Provisional status for PEPs

2014-12-17 Thread Nick Coghlan
New submission from Nick Coghlan: As per python-dev discussion [1], filing this as the home for a proposed update to PEP 1 that allows Standards Track PEPs to be granted Provisional status before moving on to Accepted/Final. The new status will be for PEPs where we want to release an initial