On Wednesday, February 6, 2013 at 8:23 PM, Nick Coghlan wrote:

The one *actual* change I will be making to the version scheme in the
next draft is to allow Fedora/Firefox/Chrome style version numbering
where there are only major releases, with no minor marker. Since the
version scheme also constrains what is permitted inside version
specifiers, this will also serve to permit things like
"Requires-Python: 2" as a shorthand for "Requires-Python: >= 2.0, < 3"
(and similar in Requires-Dist and Setup-Requires-Dist for other
projects where major releases may contain backwards incompatible
changes, and thus cross-version compatibility should be explicitly
indicated with more permissive specifiers like ">=2.6, >=3.2, <4")

Fedora/Firefox really don't have minor version numbers at all? Chrome

does have minor (actually way more than that http://d.stufft.io/image/3g0b07221P3l).

I'm not against the change in particular though. The reference impl in distutils2

protected against really high version numbers, I'm not sure what the logic behind

that was except for protecting against "dates" as a version number. Might be there

was a particular case they were making sure was rational. Only mentioning here

because major only project numbers can get big which reminded me!