I mean - PyPI is an external project. It is not a part of client/server packaging suite, so why should it depend on whenever some functionality is landed into setuptools, distutils or other stuff? I'll be pretty comfortable with setting dependencies manually for a while.
On Wed, Jun 13, 2012 at 3:48 PM, anatoly techtonik <[email protected]> wrote: > Thanks for the explanation, but it doesn't directly answer my question. > Why PyPI doesn't include dependency information? > > On Wed, Jun 13, 2012 at 3:20 PM, Donald Stufft <[email protected]> > wrote: >> setuptools is a non standard addition to Python packaging which >> is impossible to safely extract requirements in a 100% generic >> way. >> >> Distutils2 / metadata 1.2 includes a safe, good way to specify >> requirements similar to setup tools but it's not ready for primetime yet. >> >> On Wednesday, June 13, 2012 at 7:55 AM, anatoly techtonik wrote: >> >> I need to build Fabric RPM package for Fedora. I use py2pack to >> generate .spec file, which in turn uses PyPI information for it. The >> problem that PyPI completely misses information about dependencies. Is >> that intentional, broken or just not implemented? Any previous >> discussions/outcomes? >> >> http://pypi.python.org/pypi/Fabric/json - here should be a reference >> to ssh package dependency which is present in setup.py as: >> install_requires=['ssh>=1.7.14'], >> >> >> P.S. My patch queue is still awaiting review comments at this changeset >> https://bitbucket.org/techtonik/pypi-techtonik/changeset/5396f8c60d49#comments >> -- >> anatoly t. >> _______________________________________________ >> Catalog-SIG mailing list >> [email protected] >> http://mail.python.org/mailman/listinfo/catalog-sig >> >> _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
