python3-numpy shouldn't pull in *both* py3.6 and py3.7
Bug #1789199 reported by
Andreas Hasenack
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-numpy (Debian) |
Fix Released
|
Unknown
|
|||
python-numpy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
python3-numpy has a dependency on both python3.6 and python3.7:
$ dpkg -s python3-numpy|grep Depends
Depends: python3 (<< 3.8), python3 (>= 3.6~), python3.6:any, python3.7:any, python3:any (>= 3.3.2-2~), libblas3 | libblas.so.3, libc6 (>= 2.27), liblapack3 | liblapack.so.3
Python modules that work with multiple versions of python shouldn't *depend* on them.
Changed in python-numpy (Debian): | |
status: | Unknown → New |
Changed in python-numpy (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
As discussed on ubuntu-devel, the fix for this is (probably) to remove the
version-specific f2py files and recommend uses invoke pythonX.Y -m f2py (or
whatever it is) themselves.
On Tue, 28 Aug 2018 at 02:00, Bug Watch Updater <email address hidden>
wrote:
> ** Changed in: python-numpy (Debian) /bugs.launchpad .net/bugs/ 1789199 /bugs.launchpad .net/ubuntu/ +source/ python- numpy/+ bug/1789199/ +subscriptions
> Status: Unknown => New
>
> --
> You received this bug notification because you are a member of Ubuntu
> Pythoneers, which is subscribed to python-numpy in Ubuntu.
> https:/
>
> Title:
> python3-numpy shouldn't pull in *both* py3.6 and py3.7
>
> To manage notifications about this bug go to:
>
> https:/
>