On 1 April 2015 at 00:03, Nick Coghlan ncogh...@gmail.com wrote:
It's not quite that simple, I know. But until we work out how to do
something useful with a sdist that we can't do with a dev checkout,
it's hard to justify treating sdists specially.
I see it as more a matter of eventually
On Apr 01, 2015, at 04:14 PM, Thomas Güttler wrote:
Is it possible to get the dependencies of a package without full download
from pypi?
It would be kind of nice if you could get the package's metadata (e.g
egg-info/entry_points.txt) out of its PyPI JSON blob:
The answer to this is technically yes, but realistically no.
If you build Wheels and you upload a Wheel *first* and you use twine
to do so, then you will register the dependency information with
PyPI and that will be available in the JSON API. If you upload a sdist
first (or you type setup.py
Hi,
just out of curiosity:
Is it possible to get the dependencies of a package without full download from
pypi?
If you want to build a graph of dependencies this would be nice, since it would
reduce the network traffic a lot.
Regards,
Thomas Güttler
Vinay Sajip was maintaining metadata as described here, I'm sure there
are functions in distil to help fetch it.
http://distil.readthedocs.org/en/latest/packaging.html#packaging-metadata.
The most severe problem with this data is of course that it is not
always correct because the environment he
