For instance, what if PIL, python-rsvg and libev3 are dependencies of the program? These dependencies are not in pypi index, the latter two are Debian package names.
views:
353answers:
5
+2
A:
Simply don't put them in your dependencies and document that in your INSTALL or README.
Luper Rouch
2009-08-07 14:01:38
A:
If you are packaging something to be installed on Debian (as implied), the best way to manage dependencies is to package your program as a .deb and express the dependencies the Debian way. (Note, PIL is available in Debian as python-imaging.)
Ned Deily
2009-08-07 15:46:40
A:
Since the setup.py is Python code too, you just can download and run the setup.py on those packages.
juanjux
2009-08-07 20:26:10
+3
A:
You could use setuptools. setuptools allows you to add any kind of Python installable (any distutils/setuptools enabled package) as a dependency, no matter if it is on PyPI or not.
For example, to depend on PIL 1.1.6, use something like:
setup(...,
install_requires = ["http://effbot.org/downloads/Imaging-1.1.6.tar.gz"],
...)
See setuptools docs for more information.
pH
2009-08-08 18:33:17
How is PIL in turn going to cope with dependencies that are not python packages?
btw0
2009-08-09 04:43:11
setuptools is only going to run "setup.py install" as usual, any dependency handling is as per Imaging default process, so, if Imaging does it right, as it should, you get PIL correctly installed.Apart from that, you have little good choices: 1) inform your user what "native" packages he must install using the distribution default process, 2) create a distribution native package and the setup the dependencies (the ugly part is that there is a lot of distros out there).
pH
2009-08-27 12:56:33
+1
A:
I've reported this problem here :
http://mail.python.org/pipermail/python-list/2009-September/727045.html