This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, dabrahams, eric.araujo, josip, srid, tarek, techtonik
Date 2011-06-07.17:39:55
SpamBayes Score 1.974421e-06
Marked as misclassified No
Message-id <1307468396.15.0.324396170806.issue8927@psf.upfronthosting.co.za>
In-reply-to
Content
> Not all packages upload their release sources (thus metadata) to PyPI
No, it’s register that uploads metadata.

> which is why - I believe - PIP is scraping the Simple Index and
> home_page urls to get the appropriate sdist for any package.
Yes, the screen scraping in setuptools comes from the fact that not all projects upload distributions on PyPI.  (Actually, setuptools did the screen scraping before PyPI supported distributions upload.)

> I am not fully aware of what kind of packages p7g.install is supposed
> to support, though. I assume that setuptools-style projects (using
> install_requires) are not supported by p7g.install.
I think they are, or if not it’s a missing feature we want to support.  Kelsey and Alexis know more about that topic.  See recent threads on Fellowship.

> But its probably much simpler to only expose per-package dependency
> (and other metadata) through REST urls
RESTful PyPI is Alexis’ pony :)  Right know, the XML-RPC exposes the metadata, including PEP 345 Requires-Dist if the release provided it.
History
Date User Action Args
2011-06-07 17:39:56eric.araujosetrecipients: + eric.araujo, techtonik, tarek, srid, josip, dabrahams, alexis
2011-06-07 17:39:56eric.araujosetmessageid: <1307468396.15.0.324396170806.issue8927@psf.upfronthosting.co.za>
2011-06-07 17:39:55eric.araujolinkissue8927 messages
2011-06-07 17:39:55eric.araujocreate