[Catalog-sig] egg_info in PyPI

Tarek Ziadé ziade.tarek at gmail.com
Fri Sep 17 21:18:06 CEST 2010

Since egg_info results may vary depending on the platform used to built it,
how do you plan to do this so people can use these files ?

That s what we are trying to solve in pep345 by having context free metada


On Sep 17, 2010 8:43 PM, Martin v. Löwis <martin at v.loewis.de> wrote:

Here at the DZUG conference, we are planning to integrate explicit access to
setuptools metadata to the package index.

The current idea is to store the contents of the egg_info directory,
giving remote access to specific files. By default, PyPI will extract,
per release, data from the egg that may get uploaded (using the first
one if multiple eggs get uploaded). If no egg gets uploaded, a VM
based build service will generate it from a source distributions.
Tools like setuptools or distribute could also directly upload this
information, e.g. as part of the register command.

Any opinions?

Catalog-SIG mailing list
Catalog-SIG at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20100917/e85877e5/attachment.html>

More information about the Catalog-SIG mailing list