On Tue, May 31, 2016 at 9:21 AM, Ole Streicher <[email protected]> wrote: >>>> from distutils.version import StrictVersion >>>> StrictVersion("1.11.1.rc1") > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib64/python2.7/distutils/version.py", line 40, in __init__ > self.parse(vstring) > File "/usr/lib64/python2.7/distutils/version.py", line 107, in parse > raise ValueError, "invalid version number '%s'" % vstring > ValueError: invalid version number '1.11.1.rc1' > > This causes FTBS and CI failures on packages (like spectral-cube) that > use StrictVersion in their build/run time tests [1].
do you have any solution to suggest? numpy releases RC version as 1.11.1rc1 and the correct debian versioning was used for the deb package (and the same pattern was used for years in case of RC releases), so maybe the right solution is to fix the downstream packages and not use StrictVersion (which, btw, what do they use it for?) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi _______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
