[Python-Dev] Proposal to revert r54204 (splitext change)

Anthony Baxter anthony at interlink.com.au
Fri Mar 16 01:13:58 CET 2007

On Friday 16 March 2007 07:57, glyph at divmod.com wrote:
> Common parlance for the parts of a version number is:
>     major.minor.micro
> See:
> http://twistedmatrix.com/documents/current/api/twisted.python.ver
> Changing this terminology about Python releases to be more
> consistent with other projects would be a a subtle, but good
> shift towards a generally better attitude of the expectations of
> "minor" releases.

I disagree entirely. Python has major releases, and bugfix releases. 
At the moment, the major releases are of the form 2.x, and bugfix 
2.x.y. Trying to say that 2.4->2.5 is a "minor" release is just 
nonsensical. That suggests that very little new language 
development would go on, at all. Now, you might be arguing that in 
fact very little should go on (I know some people have argued this, 
I can't remember if you were one of these). My standard response to 
this is that people who really feel like this are welcome to pick a 
release, say, 2.3, and take on the process of backporting the 
relevant bugfixes back to that release, and cutting new releases, 

Anthony Baxter     <anthony at interlink.com.au>
It's never too late to have a happy childhood.

More information about the Python-Dev mailing list