Bug#1076236: python3-numpy: python3-numpy doesn't support cross-building well

[Timo Röhling]

Hi Dima,

* Dima Kogan <dko...@debian.org> [2024-08-06 10:54]:

So numpy 2.0 is coming very soon, right? If so, I'm considering this done for right now, and I'll propose a new patch when that comes. If you see anything in the current proposal that you're very much against, I'd like to know about it.

I just uploaded NumPy 2.1 to experimental, and I would like to explore the solution space around your patch further and ideally get some version of it merged before I ask the Release Team for a transition slot. I think we are still early enough in the release cycle that I can get NumPy 2.x into trixie.

Do we need to move anything else?



Package: python3-numpy
Architecture: any
Multi-Arch: allowed
Depends: python3-numpy-dev

and

Package: python3-numpy-dev
Architecture: any
Multi-Arch: same


use Build-Depends: python3-numpy:any, python3-numpy-dev. Am I wrong?




Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

So, I agree with Simon (and your initial hunch) that we cannot avoid a package split for M-A: same to be useful. I assume if we split python3-numpy-dev off of python3-numpy, we will need to move the include files, the static libraries, and the numpy.pc file. BTW, the _numpyconfig.h header is also auto-generated and contains architecture specific values (it is possible that they all happen to be identical on our current architecture set, but I would rather not rely on it). Considering that virtually all reverse dependencies currently depend on python3-numpy, I'd love to make the split in a way that allows reverse dependencies to continue doing so (otherwise we will need ~200 sourceful uploads for the transition). I think that if we have most people can continue build-depending on python3-numpy, and if you need to be able to run numpy code while cross-building, you can Everything might be complicated further by the fact that built extensions usually do not depend on python3-numpy itself, but on python3-numpy-abiX which is a virtual package provided by python3-numpy. My guess/hope is that the this will still work with Multi-Arch. I don't know for sure though.

signature.asc
Description: PGP signature