-
Is the supported versioning scheme documented somewhere? It would be helpful if PyPI (and the distutils docs) would tell users how to best name their versions to have them correctly sorted in PyPI.
2008-03-27 11:47:31 UTC in Python Package Index
-
When I update the visibility of existing package versions, the return page shows the old state instead of the updated state. This is confusing and error prone as an accidental re-commit will change the setup back to the old state. To do additional changes afterwards, one first has to take care to reload the page, otherwise, all previous changes will be lost.
2008-03-27 11:43:55 UTC in Python Package Index
-
Hiding the last version would still require manual interaction if you want to keep older versions visible.
My current work-around is: keep the visibility setup page open during registration and commit it afterwards (unchanged). That way, PyPI will set all previously existing versions to their original state. That's an annoying work-around, but not any more work than your solution would...
2008-03-27 11:40:30 UTC in Python Package Index
-
scoder committed patchset 196 of module mathdom to the MathDOM CVS repository, changing 1 files.
2008-03-11 18:18:26 UTC in MathDOM
-
scoder committed patchset 195 of module mathdom to the MathDOM CVS repository, changing 1 files.
2008-03-11 18:16:35 UTC in MathDOM
-
scoder committed patchset 194 of module mathdom to the MathDOM CVS repository, changing 1 files.
2008-03-11 18:16:05 UTC in MathDOM
-
scoder committed patchset 193 of module mathdom to the MathDOM CVS repository, changing 1 files.
2008-03-11 18:10:05 UTC in MathDOM
-
Martin, I found at least one project that uses "a" and "b" as postfix for *increasing* patch level version numbers. In that case, it's impossible to distinguish them from the more common "alpha" and "beta" markers. So, now I know what you mean with "too many different ways". I guess you're right that there isn't really a way to do it "correctly"...
2008-02-14 14:44:52 UTC in Python Package Index
-
I really don't think it's that hard to do. All there is to it is split version numbers into sequences of numbers, dots and letters and compare the resulting tuples. Done. I wouldn't even consider that worth a PEP, not even the fine tuning that might be doable afterwards.
2008-02-01 20:05:21 UTC in Python Package Index
-
PyPI doesn't sort alpha/beta versions before the final (postfix-less) release, as you can see here:
http://pypi.python.org/pypi/lxml
Also note the incorrect "latest version" link at the top of this page, that links from "2.0" to "2.0beta2":
http://pypi.python.org/pypi/lxml/2.0
I think PyPI should be intelligent enough to split these not-so-uncommon postfixes from the actual version.
2008-02-01 18:23:02 UTC in Python Package Index
