<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ben Finney wrote:
<blockquote cite="mid87ljtmh6bd.fsf@benfinney.id.au" type="cite">
<pre wrap="">Gerry Reno <a class="moz-txt-link-rfc2396E"
href="mailto:greno@verizon.net"><greno@verizon.net></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">We have an application, foo-5.0.0, and we want to put out some
pre-release candidates for testing, so we set the version to
"5.0.0_rc1" in setup.py.
</pre>
</blockquote>
<pre wrap=""><!---->
That's where your problems start (as you no doubt surmised). If you
want version numbers to compare in a certain order, you should name
them so that the version string will trivially compare in that order.
</pre>
</blockquote>
In many instances we don't get to make that decision when we join
projects already in motion. Otherwise, I would not have bothered to
post the problem to the list. The fact is that many applications use
version string constructs such as I illustrated, "5.0.0_rc1" when they
create their release candidates. And yes, the final release, "5.0.0",
is not lexically superior. But, as much as I might like that everyone
would not do this, I cannot change the whole world which has developed
a habit of such things. So I am looking for a solution that works with
the world as it is.<br>
<br>
Regards,<br>
Gerry<br>
<br>
</body>
</html>