[Python-Dev] Deprecation policy (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue Nov 29 13:59:48 CET 2011
- Previous message: [Python-Dev] Deprecation policy
- Next message: [Python-Dev] Deprecation policy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 29 Nov 2011 14:46:06 +0200 Petri Lehtinen <petri at digip.org> wrote:
Michael Foord wrote: > We tend to see 3.2 -> 3.3 as a "major version" increment, but that's > just Python's terminology.
Even though (in the documentation) Python's version number components are called major, minor, micro, releaselevel and serial, in this order? So when the minor version component is increased it's a major version increment? :)
Well, that's why I think the version number components are not correctly named. I don't think any of the 2.x or 3.x releases can be called "minor" by any stretch of the word. A quick glance at http://docs.python.org/dev/whatsnew/index.html should be enough.
Regards
Antoine.
- Previous message: [Python-Dev] Deprecation policy
- Next message: [Python-Dev] Deprecation policy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]