Bradley M. Froehle, 01.08.2012 18:35:
> Yes, this versioning has also impacted mpi4py which had to add some pretty 
> ugly code in setup.py to work around it:
> 
> https://code.google.com/p/mpi4py/source/detail?r=841e9df
> 
>> I am not sure what is the status on PEP 386 [1] (not yet adopted afaik)

It's in state "Accepted".


> but it might be worthwhile following it and/or existing
>> disutils.version.StrictVersion since having
>>
>> In [2]: Cython.__version__
>> Out[2]: '0.17.beta1'
>>
>> is not digested well by some depending projects -- there were 2 failures to
>> build against this beta release of Cython in Debian due to difficulty with
>> parsing the version -- bzr and xpra I believe [2]. So may be it is worth
>> making it '0.17b1' (and use corresponding tags accordingly)?

I guess so. That would fit the StrictVersion scheme.

Stefan

_______________________________________________
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel

Reply via email to