Benjamin, what are you thoughts on usage of the "needs backport to 2.7" label? For most of the PRs I've reviewed I tend to avoid adding it myself, but I've seen it used periodically. It seems to be used rather infrequently (, but I'm not entirely clear on when it should be used, particularly for documentation-related PRs.

Also, is there an official date when the label will be removed? Removing the backport label seems to generally be at the discretion of the release manager for that version, but I was curious as to whether it would be removed on the sunset date or prior to then. Without the label, backport PRs can still be opened manually of course, but removing it would probably help to discourage 2.7 backports.

On Mon, Sep 9, 2019 at 9:38 AM Benjamin Peterson <> wrote:
Hi all,
It's finally time to schedule the last releases in Python 2's life. There will be two more releases of Python 2.7: Python 2.7.17 and Python 2.7.18.

Python 2.7.17 release candidate 1 will happen on October 5th followed by the final release on October 19th.

I'm going to time Python 2.7.18 to coincide with PyCon 2020 in April, so attendees can enjoy some collective catharsis. We'll still say January 1st is the official EOL date.

Thanks to Sumana Harihareswara, there's now a FAQ about the Python 2 sunset on the website:

Python-Dev mailing list --
To unsubscribe send an email to
Message archived at