On tor, 2011-10-13 at 22:01 +0200, Jakub Wilk wrote: > * Peter Eisentraut <[email protected]>, 2011-07-18, 14:34: > >When you use the entry_points argument of setup(), Python scripts for > >/usr/bin are automatically generated. These scripts import > >pkg_resources, and therefore the containing package should have a > >run-time dependency on python-pkg-resources. In my experience, this is > >easy to forget and it's not really documented, because when you use > >easy_install, python-setuptools depends on python-pkg-resources anyway, > >so you don't really need to worry about it. Only when you use Debian > >packages and uninstall python-pkg-resources (because apt/aptitude tell > >you it's no longer needed), things start to break. > > > >Perhaps dh_python2 could simply look whether > >*.egg-info/entry_points.txt exists, and if so add python-pkg-resources > >to ${python:Depends}. > > FWIW, I maintain a package[0] that has entry points, but it doesn't have > runtime dependency on python-pkg-resources. (But then, I am a happy > non-user of dh_python2. :P) > > > [0] python-sphinx
Well, that package takes explicit steps to overwrite the automatically generated entry point scripts. In that case, you might as well remove the entry point generation from setup.py. If you're concerned, perhaps dh_python2 could have an extra option to disable automatic dependency detection. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
