Package: python3-numpy
Version: 1:1.24.2-2
Followup-For: Bug #1003805

Dear Maintainer,

I second this request.  By a quick survey of other « python3-xxxx » packages 
installed on my
system, they all depend on python3:any (and not on python3.##:any).  This means 
that *SOME*
version of python3 will be installed, which, in almost all cases, is enough. 
Usually, it will
be the current default version: today, 3.11 on sid, and when that bumps up to 
3.12, then on
most systems, all python3-xxx packages will switch to 3.12 in a manner 
essentially transparent
to the user.
If the user absoultely wants to use 3.12 today, there is nothing that prevents 
him or her to
install python3.12 manually, and all python3-xxxx packages will also 
byte-compile to that
automatically.
On the other hand, with the hard Depends: of python3-numpy, the user is simply 
unable to
decide NOT to isntall python3.12 , and this is indeed annoying to some.

So, I request that you reduce the dependence to python3:any alone, as for other 
python3-xxxx
packages.

Yours,
Itaï.




-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-numpy depends on:
ii  libatlas3-base [liblapack.so.3]  3.10.3-13
ii  libblas3 [libblas.so.3]          3.11.0-2
ii  libc6                            2.37-13
ii  liblapack3 [liblapack.so.3]      3.11.0-2
ii  python3                          3.11.6-1
ii  python3-pkg-resources            68.1.2-2
ii  python3.11                       3.11.7-1
ii  python3.12                       3.12.1-1

python3-numpy recommends no packages.

Versions of packages python3-numpy suggests:
ii  gcc             4:13.2.0-2
pn  gfortran        <none>
ii  python3-dev     3.11.6-1
pn  python3-pytest  <none>

-- no debconf information

Reply via email to