Home Original page

[python-committers] Closing the 2.6 branch?

Barry Warsaw barry at python.org
Wed Oct 30 16:54:25 CET 2013 
On Oct 31, 2013, at 01:28 AM, Nick Coghlan wrote:

>There's a trick to get the PEP 0 generator to move the release PEP to the
>historical section, too. I'd have to look at the source code to remember
>what it is, though.

        elif pep.type_ == 'Informational':
            # Hack until the conflict between the use of "Final"
            # for both API definition PEPs and other (actually
            # obsolete) PEPs is addressed
            if (pep.status == "Active" or
                "Release Schedule" not in pep.title):
                info.append(pep)
            else:
                historical.append(pep)

So PEP 361 (the 2.6/3.0 release schedule PEP) actually does end up in the
Historical bin.  The PEP itself probably should have remained Active until
yesterday.

Do we want an explicit state for Status: Final -> Historical?

(TBH, I don't care enough to do any work on it. ;)

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-committers/attachments/20131030/6e8921d3/attachment.sig>
More information about the python-committers mailing list