[Python-modules-team] Bug#825900: Bug#825900: python-numpy: version number breaks distutils.version.StrictVersion

[Sandro Tosi]

please dont reply only to me, and always keep the bug in the loop; I
didnt add the bug back in the recipients and it would disclose your
private email, but you can forward my reply

On Tue, May 31, 2016 at 10:38 AM, Ole Streicher <olebole at debian.org> wrote:
> Hi Sandro,
>
> On 31.05.2016 11:28, Sandro Tosi wrote:
>> do you have any solution to suggest?
>
> Still not; after numpy upstream pointed me to PEP-440, I forwarded this
> to the spectral-cube upstream [1]. We will probably find a solution for
> spectral-cube.
>
> [1] https://github.com/radio-astro-tools/spectral-cube/issues/308
>
>> 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?)
>
> They try to catch changes in numpy over the years to be compliant to
> older numpy versions as well. The source code in question is here:
>
> https://github.com/radio-astro-tools/spectral-cube/blob/master/spectral_cube/np_compat.py
>
> This is still useful to allow backporting to Debian Jessie, so I
> wouldn't like to remove it.

then use LooseVersion instead of StrictVersion?


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi