* Matthias Klose <d...@debian.org>, 2013-05-21, 17:55:
namespace packages aren't an issue anymore in python3, and for python2
it would be better to ship these files into separate binary packages.
these aren't that many, and it would be much better for the robustness.
nothing to do anymore about these in maintainer scripts.
We have about ~60 packages which ship files in /usr/share/python/ns/,
which is quite a bit. That said, most of them don't need __init__.py at
all, because the namespace would be created at runtime via *-nspkg.pth
files.
The only namespaces for which appropriate *-nspkg.pth don't exist are:
* flaskext (python-flaksext.wtf): flaskext/__init__.py is already
shipped by python-flask, so not a problem.
* r2 (python-radare2): no other users of the namespace AFAICS, so it
could ship __init__.py directly in .deb.
* dummy (python-van.pydeb)
* zope.app (python-van.pydeb) - these two look like a bug in dh_python2.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130521180705.ga8...@jwilk.net
