2009/6/4 P.J. Eby <pje@telecommunity.com>:
In setuptools' case, the original intent was to be compatible with projects that do have things like '2.4-1' - e.g., because they're a wrapper of a library whose version is 2.4, and the wrapper is the first version of that. If the library then releases a '2.4.1', the wrapper for that is then '2.4.1-1'. However, some projects (see Jean-Paul Calderone's recent questions here) have things like '2.4+1' as a patch level.
I *suppose*. :) Personally I just tack on an external field the main version number for that. For example: http://code.google.com/p/python-markdown2/source/browse/trunk/lib/markdown2.... version 1.0.1.12 where the first three numbers are those of the Perl Markdown.pl on which this is based. Granted that if Markdown.pl 1.0.1.1 came out it would be a little awkward, but that kind of thing (where the wrapped library adds another version bit) would be rare, I'd imagine. Trent -- Trent Mick trentm@gmail.com