pypi and dependencies
donald.stufft at gmail.com
Tue Mar 20 13:13:36 CET 2012
packaging (in 3.3) and distutils2 (2.x-3.2) is a new metadata format for python
packages. It gets rid of setup.py and it includes a way to specify the requirements
that your package needs. This will show up on PyPI/Crate.
On Tuesday, March 20, 2012 at 8:01 AM, Andrea Crotti wrote:
> On 03/20/2012 11:18 AM, Ben Finney wrote:
> > Andrea Crotti<andrea.crotti.0 at gmail.com (mailto:andrea.crotti.0 at gmail.com)> writes:
> > > When I publish something on Pypi, is there a way to make it fetch the list
> > > of dependencies needed by my project automatically?
> > >
> > > It would be nice to have it in the Pypi page, without having to look at the
> > > actual code..
> > >
> > Sadly, no. The metadata available for packages on PyPI does not include
> > information about the dependencies.
> > (I'd love to be wrong about that, but I'm pretty certain that for most,
> > if not all, packages that's the case.)
> > > Any other possible solution?
> > All the solutions I've seen involve fetching the full package in order
> > to unpack it and *then* parse it for dependencies.
> > This is very sub-optimal, and I believe people are working on it; but
> > fixing it will at least require adjustment to all existing packages that
> > don't have dependencies in their metadata.
> Yes that's not so nice, many projects write clearly the dependencies in
> the README file,
> but that's annoying because it might get outdated.
> And it's also sad that it's not automatically fetched from setuptools,
> because it's just
> python setup.py egg-info && cat package.egg-info/requirements.txt
> to actually extract them.
> Should I file a bug maybe or is completely not feasible?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-list