#998820 lintian: overly generic python modules /usr/lib/python3/dist-packages/benchmarks/*.py

Package:
lintian
Source:
lintian
Submitter:
Andreas Beckmann
Date:
2024-06-03 07:42:03 UTC
Severity:
normal
#998820#5
Date:
2021-11-08 09:36:53 UTC
From:
To:
python3-satpy ships (among others)

drwxr-xr-x root/root         0 2021-11-07 11:56 ./usr/lib/python3/dist-packages/benchmarks/
-rw-r--r-- root/root       752 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/__init__.py
-rw-r--r-- root/root      2632 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/abi_l1b_benchmarks.py
-rw-r--r-- root/root      2671 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/ahi_hsd_benchmarks.py
-rw-r--r-- root/root      5817 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/fci_benchmarks.py
-rw-r--r-- root/root      2594 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/seviri_hrit_benchmarks.py
-rw-r--r-- root/root      2811 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/utils.py
-rw-r--r-- root/root      4121 2021-11-04 02:43 ./usr/lib/python3/dist-packages/benchmarks/viirs_sdr_benchmarks.py

This has caused file conflicts with other packages doing the same
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991981

Probably ./usr/lib/python3/dist-packages/benchmarks/__init__.py should
be "blacklisted" as overly generic and the remaining files under
benchmarks should be discouraged.
(But benchmarks/$MODULE/*.py should probably be OK.)


Andreas
#998820#10
Date:
2022-06-02 00:50:25 UTC
From:
To:
Please add this file to the list of overly generic python modules, too:

/usr/lib/python3/dist-packages/docs/conf.py


Andreas
#998820#15
Date:
2022-08-30 21:10:15 UTC
From:
To:
and that:

/usr/lib/python3/dist-packages/ez_setup.py

(found in python3-pymodbus (2.1.0+dfsg-2) (bullseye) and
python3-astroalign (2.4.1-2) (sid))


Andreas
#998820#20
Date:
2022-10-10 11:44:34 UTC
From:
To:
and that one as well:

/usr/lib/python3/dist-packages/tools/__init__.py

found in python3-capirca 2.0.3-2 and python3-breezy 3.3.0+bzr7660-1


Andreas
#998820#25
Date:
2022-10-18 11:42:25 UTC
From:
To:
Another one:

/usr/lib/python3/dist-packages/setup.py

found in i8c 0.0.6-1 and mate-tweak 22.10.0-1


Andreas
#998820#30
Date:
2024-06-03 05:51:48 UTC
From:
To:
Then we also have

/usr/lib/python3/dist-packages/build/lib/doc/conf.py
                                         ^^^
e.g. nxtomo 1.2.3-2

usr/lib/python3/dist-packages/build/lib/docs/conf.py
                                        ^^^^
e.g. pipenv 2023.12.1+ds-1


Andreas
#998820#35
Date:
2024-06-03 06:17:31 UTC
From:
To:
and /usr/lib/python3/dist-packages/docs/conf.py

e.g. in python3-specreduce 1.4.0-1


Andreas
#998820#40
Date:
2024-06-03 07:37:58 UTC
From:
To:
that are installed under /usr/lib/python3/dist-packages/, but outside
the package directory? E.g. all files from python3-nxtomo in
/usr/lib/python3/dist-packages/, but outside
/usr/lib/python3/dist-packages/nxtomo/. I guess such approach may
produce false-positives for plugin packages.

Another solution would be to simply warn about specific paths, such as:

/usr/lib/python3/dist-packages/build/*
/usr/lib/python3/dist-packages/docs/*
/usr/lib/python3/dist-packages/__init__.py
...

Does it make sense to name lintian tag
'python-package-installs-overly-generic-path'?

Best,
Andrius