Thanks all for clarifying! -Collin

On Sat, Aug 25, 2018 at 2:50 PM Benjamin Peterson <benja...@python.org>
wrote:

> I was operating under the optimistic assumption whatever the precise time
> of 2.7's official demise would only be an amusing piece of trivia for a
> world of happy Python 3 users.
>
> It's still to early to promise exact release dates; that will depend on
> the day-to-day schedules of the release manager and binary builders circa
> January 2020. A conservative assumption is that no 2.7 changes that land
> after December 31 2019 will ever be released.
>
> We could make the last release of 2.7 in July 2020. But what does that buy
> anyone?
>
> On Thu, Aug 23, 2018, at 11:53, Collin Anderson wrote:
> > Hi All,
> >
> > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL
> > date was recently set to Jan 1st, 2020.
> >
> > My understanding was Python releases get 5 years of support from their
> > initial release, and Python 2.7 was extended an additional 5 years.
> >
> > Python 2.7 was originally released on 2010-07-03, and with an original
> EOL
> > of 2015-07-03. Extended 5 years, shouldn't the EOL be 2020-07-03?
> >
> > Also, this statement is a little unclear to me:
> >
> > > Specifically, 2.7 will receive bugfix support until January 1, 2020.
> All
> > 2.7 development work will cease in 2020.
> >
> > This statement makes it sound like bugfixes end on Jan 1st, but seems to
> > leave open the possibility that security fixes could continue through the
> > year.
> >
> > Thanks!
> > Collin
> > _______________________________________________
> > Python-Dev mailing list
> > Python-Dev@python.org
> > https://mail.python.org/mailman/listinfo/python-dev
> > Unsubscribe:
> > https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to