techtonik at gmail.com
Wed Jun 13 15:20:49 CEST 2012
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 <techtonik at gmail.com> 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 <donald.stufft at gmail.com> wrote:
>> setuptools is a non standard addition to Python packaging which
>> is impossible to safely extract requirements in a 100% generic
>> 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
>> http://pypi.python.org/pypi/Fabric/json - here should be a reference
>> to ssh package dependency which is present in setup.py as:
>> P.S. My patch queue is still awaiting review comments at this changeset
>> anatoly t.
>> Catalog-SIG mailing list
>> Catalog-SIG at python.org
More information about the Catalog-SIG