Groups > comp.lang.python > #30526 > unrolled thread

EOL for Python 3.2?

Started by	David Dillard <davidedillard@gmail.com>
First post	2012-09-29 13:03 -0700
Last post	2012-09-30 01:41 -0400
Articles	3 — 3 participants

Back to article view | Back to comp.lang.python

  EOL for Python 3.2? David Dillard <davidedillard@gmail.com> - 2012-09-29 13:03 -0700
    Re: EOL for Python 3.2? Andrew Berg <bahamutzero8825@gmail.com> - 2012-09-29 15:26 -0500
    Re: EOL for Python 3.2? Terry Reedy <tjreedy@udel.edu> - 2012-09-30 01:41 -0400

#30526 — EOL for Python 3.2?

From	David Dillard <davidedillard@gmail.com>
Date	2012-09-29 13:03 -0700
Subject	EOL for Python 3.2?
Message-ID	<f5fba756-2663-4cf1-9d7c-b80fedcff0ad@googlegroups.com>

With the release of Python 3.3.0 does that mean the 3.2.x line is now end of life?

I've looked for some sort of end of life policy on python.org, but was unable to find one.

[toc] | [next] | [standalone]

#30527

From	Andrew Berg <bahamutzero8825@gmail.com>
Date	2012-09-29 15:26 -0500
Message-ID	<mailman.1653.1348950396.27098.python-list@python.org>
In reply to	#30526

On 2012.09.29 15:03, David Dillard wrote:
> With the release of Python 3.3.0 does that mean the 3.2.x line is now end of life?
No. Old releases get security fixes for years.

> I've looked for some sort of end of life policy on python.org, but was unable to find one.
http://www.python.org/download/releases/

If you go to a version, it will tell you the status. For example, 3.1.x
and 2.6.x still get security fixes, but 2.5.6 is the absolute last
release of 2.5 - it will NOT receive updates of any kind. Unless the
page states otherwise, it is pretty safe to assume that the release is
maintained.
-- 
CPython 3.3.0 | Windows NT 6.1.7601.17835

[toc] | [prev] | [next] | [standalone]

#30542

From	Terry Reedy <tjreedy@udel.edu>
Date	2012-09-30 01:41 -0400
Message-ID	<mailman.1662.1348983687.27098.python-list@python.org>
In reply to	#30526

On 9/29/2012 4:03 PM, David Dillard wrote:
> With the release of Python 3.3.0 does that mean the 3.2.x line is now
> end of life?

The next release (3.2.4, soon) will by the last 3.2 bugfix. Then 3 years 
for security fixes.

> I've looked for some sort of end of life policy on python.org, but
> was unable to find one.

Don't know where written, but last 3.x bugfix about the time of 
3.(x+1).0 and 3 years security is standard.

-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

csiph-web

EOL for Python 3.2?

Contents

#30526 — EOL for Python 3.2?

#30527

#30542