On Fri, Jun 5, 2009 at 2:43 PM, Paul Moore<[email protected]> wrote: > I'd rather the PEP said "This is how version numbers work (simple, > non-controversial spec here), and this is the standard API for > manipulating them", and then projects that want to conform to the > standard migrate if needed.
That's exactly the goal. Maybe there's a missing introduction on how version numbers works Not a standard at first, but the principles of releasing a dev release, an alpha, and so on.. > But I acknowledge that I have no personal requirement for any of this, > so the only interest I have is an aesthetic one of *not* seeing > overcomplicated, difficult to understand, specifications become part > of the Python stdlib. Well if the specification is difficult to understand or overcomplicated it'll fail for sure. But so far, besides that very specific case for the post-release dev tag, I don't find it complicated at all. Another win I can see is that it will help developers use better versions numbers for their projects imho. Regards Tarek _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
