On Thu, Jan 20, 2011 at 4:40 AM, Barry Warsaw wrote:
> On Jan 19, 2011, at 12:16 AM, Nick Coghlan wrote:
>
>>For the release schedule PEPs it means "done and dusted" (similar to
>>the meaning for ordinary PEPs). For the API standardisation PEPs (like
>>WSGI) it instead means the spec has been lock
On Jan 19, 2011, at 12:16 AM, Nick Coghlan wrote:
>For the release schedule PEPs it means "done and dusted" (similar to
>the meaning for ordinary PEPs). For the API standardisation PEPs (like
>WSGI) it instead means the spec has been locked down and any changes
>will require a new PEP. This caused
python-checkins watchers would be aware that I just checked in a few
changes to the PEP 0 generator (and a few PEP statuses) to start
tidying up the first two sections of PEP 0. The old release schedule
PEPs and similarly obsolete files have been moved down to a new
historical section later in the