[email protected] wrote:
> While I like the use of "rc" for release candidate, doesn't this lead to some 
> ambiguity where a,b,c are seen as interim releases with "rc" sorting after 
> all of these?
> 
> I don't have an objection to [a-q] OR 'rc' if we're reserving "rc" for 
> release candidate and only "rc" for that purpose.
> 
> Otherwise, the sorting becomes ambiguous so if "c" means candidate then "rc" 
> can't also or we don't know, for sure, that blah-rc comes AFTER blah-c; it's 
> ambiguous.

The meaning of the version modifiers is not really relevant here.
distutils just needs to be able to compare them and not make
mistakes in those comparisons.

Also note that distutils won't be comparing apples and oranges,
only the version numbers of a single package.

Given that package authors typically don't change their versioning
scheme within a single release cycle, there's nothing much to
worry about, IMO.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Nov 25 2009)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
_______________________________________________
Distutils-SIG maillist  -  [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to