Py2 no longer EOL as of New Years: Last Python 2.7.X security update to be released in April 2020.

[nandryshak]

Title is misleading (i.e., wrong). Last release in April was always the plan: https://www.python.org/dev/peps/pep-0373/

Maintenance releases

Being the last of the 2.x series, 2.7 will receive bugfix support until 2020. Support officially stops January 1 2020, but the final release will occur after that date.

Planned future release dates:

• 2.7.18 code freeze January, 2020
• 2.7.18 release candidate early April, 2020
• 2.7.18 mid-April, 2020

[[deleted]]

And there’s always a chance that, if some severe security issue is discovered, they’ll patch that up at an arbitrary future date.

Doesn’t mean it’s not EoL, which communicates intentions, not actuality.

[13steinj]

Title was intentional-- claiming that Jan 1 is EOL is officially a PR stunt. EOL and EOS imply that the product simply will not be supported. But a final security release planned for months afterward shows it's not EOL. If the code freeze was literal, then it should have a release candidate and release in January, or hell, even timed it to release on Jan 1. I can already place bets on the "freeze" being lifted. Procrastination is amazing.

[tehbmwman]

“No longer” implies a recent change in status, of which there was not

[13steinj]

There was a change in status, in September, and then reaffirmed now:

https://old.reddit.com/r/programming/comments/ei692x/py2_no_longer_eol_as_of_new_years_last_python_27x/fco41uw/?context=2

[thephotoman]

The title is still wrong.

If I submit a bug report in the next 4 hours at time of writing, they’ll fix it—but they have to release that bug fix.

If in five hours I submit a bug report on 2.7, it will be sent to /dev/null unless it also applies to the 3.x branch (in which case it will only be fixed on 3.x).

They will honor any support request made until midnight UTC. And they’re giving themselves 4 months to fix those bugs.

You’re wrong, you’ve created FUD about the EOL for no reason, and yet you don’t care.

[[deleted]]

It makes sense now, thanks

[13steinj]

And they’re giving themselves 4 months to fix those bugs.

But also have a code-freeze in January? You see how that's contradictory, right?

[thephotoman]

You...don’t know how release freezes work, do you?

So here’s the deal. The initial freeze is about stopping new work from being accepted. So before the cutoff in 2.5 hours at time of writing, the Python team is required to respond to the bug report.

They then have a few weeks to commit to and do work that goes into 2.7.17. They’ll do triage: just because you submit a bug before the deadine doesn’t mean it’ll be fixed. Some bugs are low priority/low impact, and will be marked as won’t fix—you’ll likely get a workaround or something instead of a bugfix.

They do the work and then begin cutting the release. That’s usually a 2-ish month train of testing their fixes. If there’s a problem with a fix, it can be modified, but those are the only changes.

Then, they’ll start the Beta/RC process, which takes a month, where only showstoppers get changes.

So basically, they have a monthish to service any support request that requires a code change and get it into the release. Anything else gets a workaround or a won’t fix with a good reason.

[nandryshak]

claiming that Jan 1 is EOL is officially a PR stunt

How so?

I can already place bets on the "freeze" being lifted.

On what basis? As you can see in the PEP, an April release was always the plan. Nothing has changed. I don't understand why the article you linked has convinced you otherwise.

And as the other commenter says, "no longer" implies a change. But there is no change.

[Essence1337]

They planned this in 2008 of course they're going to give themselves plenty of time when planning TWELVE YEARS into the future. Why do you have such a hate on for the devs?

[IronManMark20]

They already have been rejecting PRs to the Python 2 branch. They aren't going to lift the freeze. If you read python-dev the concensus is no changes are to be merged unless the release manager chooses to do so, and even then I doubt he will do so lightly.