[Catalog-sig] egg_info in PyPI

[Tarek Ziadé]

2010/9/20 M.-A. Lemburg <mal at egenix.com>:
> Tarek Ziadé wrote:
>> On Mon, Sep 20, 2010 at 9:26 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>>> IMHO, most of this has been resolved by means of the XML-RPC
>>>> interface via the .release_data() method:
>>>>
>>>> http://wiki.python.org/moin/PyPiXmlRpc
>>>>
>>>> If there's something missing, we should add it there.
>>>
>>> Very clearly, most of egg-info is missing there. However, I
>>> sense that people are very opposed to adding it there.
>>>
>>> I merely asked whether it was ok to expose the egg-info
>>> data at all, and was met with strong opposition - nobody
>>> actually asked what specific API to expose them I had in
>>> mind.
>>
>> If the use case is to provide a way to build a dependency graph just
>> by querying PyPI, that's exactly what we have in mind in pep 345.
>
> I think I lost you there... .release_data() does provide the
> PEP 345 meta-data, at least according to the documentation.

Yes. I am the one who added it there.

And the information contained will let you have the list of
dependencies for a packages whatever your platform is -- that's the
goal of the work we did in the metadata area.

So uploading another metadata format like egg_info that contains
platform-dependent information to provide the same feature but in a
non-accurate way, is to be avoided -- no matter how it's exposed. As
other mentioned, it is often similar on every platform. but there's no
other mechanism than running egg_info again to be 100% sure of that..

True, there's no package yet that is using PEP 345 since its being
released now. But that's not a good reason imho to push new features
at PyPI based on the old format, knowing that these features are
existing in the new one, and knowing that the old format has issues as
explained.

Like py2 vs py3, I think all part of the packaging eco-system should
focus its energy on the new things we are building and just maintain
the old format and avoid spending energy and time on it. But that's my
own personal opinion :-)


Regards
Tarek
-- 
Tarek Ziadé | http://ziade.org