[Catalog-sig] egg_info in PyPI

Tarek Ziadé ziade.tarek at gmail.com
Mon Sep 20 22:18:41 CEST 2010

On Mon, Sep 20, 2010 at 9:57 PM, M.-A. Lemburg <mal at egenix.com> wrote:
>> That's how I would have implemented it. Alas, this very
>> idea was just shot down.
> I think most of the response was targeted at the EGG-INFO
> meta-data format, not the information itself.

No, it's also the information itself. requires.txt for instance can
vary depending on the platform that was initially used to build
egg-info. IOW it means that you push data that is created at build
time at PyPI. Publishing those files and calling them metadata is

So the status-quo where people need to rebuild egg_info to get the
metadata for their platform is preferable, until PEP 345 gets used,
since is was partially created to solve this.


More information about the Catalog-SIG mailing list