[Python-Dev] Policy about old Python versions

"Martin v. Löwis" martin at v.loewis.de
Thu Nov 4 18:51:56 CET 2004

Batista, Facundo wrote:
> Sometimes, reviewing bugs, I found some ones referring problems about old
> Python versions.
> Is there a policy about supporting old Python versions? At some time an old
> version becomes "deprecated"?
> For example, an open bug about a problem of Python 2.1, that is solved in
> Python 2.2 and subsequents, when should be closed?

It is (IMO) fine to close anything now that is fixed in 2.3 and newer.
The proper "Resolution" is "Fixed", with a Comment "Fixed in 2.3".

There likely will be one more 2.3 release, so you might not want to
close something as "Fixed in 2.4" that is still incorrect in 2.3;
instead, consider backporting the patch (we are all volunteers, so
this is clearly not mandatory). If you find something is fixed in
2.4, but have no time to find out how precisely it was fixed, still
leave a comment saying so.

After the next 2.3 release, people are still free to backport to older
branches - after all, distributors may chose to roll out patches
collected even after the last release of some 2.x. However, in general,
expect that 2.3 and older needs no further attention RSN, and
"backporting" will mean "to 2.4".


More information about the Python-Dev mailing list