On lun, 2024-04-15 at 20:37 +0000, Atri Bhattacharya wrote:
daniel.garcia@suse.com wrote:
On vie, 2024-04-12 at 14:44 +0000, Atri Bhattacharya wrote:
Hi, With numpy 2.0 ostensibly releasing soon [1] and breaking backward compatibility with numpy 1.2X [2], I wonder what the plan for numpy packages will be for openSUSE. Will we maintain two different series of numpy as, for instance, `python-numpy` and `python-numpy2`? This will perhaps be the least breaking path to take for packages dependent on `numpy` — which will probably take a while to catch up — but I understand if the additional maintenance efforts this will require compel otherwise. Also, as someone who maintains a few packages in d:l:p:numeric, I would be happy to help out if needed (maintaining the 1.x branch or any other way).
I would go for keeping python-numpy as the latest version (in this case, 2.0) and create a new package called python-numpy_1. Any package that depends on old numpy can just add the version limit to the spec file like:
Requires: python-numpy < 2
..which would entail manual fixes for a rather large number of specfiles. What would be the benefit, if I may ask, as opposed to using `python- numpy2` as I suggested above?
The benefit is that we will keep the upstream name for the package and in the future we just need to drop python-numpy_1. If we do it the other way, at some point we will need to rename the package or we will keep the package name mismatch forever. I mean, if upstream doesn't change the name to numpy2, all the projects that depends on it should also update their dependencies to pin the version when it's released. I would like to keep the package name coherent with the upstream name provided in pypi.org -- Daniel García Moreno Python Packager