[Distutils] [RFC] PEP 345 and PEP 386 updates
chris at simplistix.co.uk
Tue Oct 27 17:47:15 CET 2009
Tarek Ziadé wrote:
>> I thought the plan was to stick with major.minor and "==", "!=", "in" and
>> "not in" until PEP 386 was accepted, then switch over to having all versions
>> (including Python's) be some sort of Version object, at which point we can
>> have richer version comparisons, with all of the existing uses being
> Yes that's the plan too. PEP 345 is not updated yet, but that is
> clearly stated in PEP 386.
So why don't we just pause for a while, get 386 done, implemented in and
then come back to 345?
I can't see why we'd want to not treat a Python version like any other
package version, but if we need 386 to get that, then lets do that
rather than finding convoluted ways to work around the problem...
Simplistix - Content Management, Batch Processing & Python Consulting
More information about the Distutils-SIG