[Python-modules-team] Bug#643873: Bug#643873: Making Numpy transition less painful
morph at debian.org
Mon Nov 7 22:48:09 UTC 2011
On Tue, Nov 1, 2011 at 22:51, Jakub Wilk <jwilk at debian.org> wrote:
> * Sandro Tosi <morph at debian.org>, 2011-11-01, 12:52:
>>>>> Dependencies generated by dh_numpy
>>>>> dh_numpy would generate dependency either on "python-numpy-abi$N" (by
>>>>> default) or on "python-numpy-api$N" (if a special option, say, --strict, is
>>> I just realized that, in order to make packages using Cython happy, the
>>> first one will have to be:
>>> "python-numpy-abi$N, python-numpy (>= $V)"
>>> where $V is the first version with the current API. 
>> Mh ok, so we need to keep 3 versions information: the ABI $N, the API $N,
>> and the version $V that introduced API $N - did I get it correctly?
> Yes. Though it'd better not to use same name for two distinct variables
> (yes, I know, I made the same mistake myself). :P
I was just using your "convention" (and mentally complaining it was
not $M $N) :P
>>>>> Gracefully handling the upcoming transition
>> Ok, so we should start like this:
>> - implement this proposal in the version currently in sid
> Here we could:
> - wait until new dh_numpy hits testing
>> - round of binNMUs
>> - wait for transition to testing?
>> - port the code to 1.6.1 package in experimental
>> - upload it to sid
>> - reiter
>> is that correct?
> Yes, sounds about right.
I think we just need to see Piotr's reply to the pydist/non-pydist
question and then we're probably ok with this solution?
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
More information about the Python-modules-team