[Catalog-sig] egg_info in PyPI

M.-A. Lemburg mal at egenix.com
Mon Sep 20 21:57:52 CEST 2010


"Martin v. Löwis" 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.

Well, "most" depends on what you view as really important
meta-data.

Here's an example EGG-INFO dir:

dependency_links.txt

 This file lists extra links to search for dependencies. This could
 be added to the meta-data.

native_libs.txt

 This is not really needed, since I think we all agree that
 keeping eggs zipped up when installing them is not a good idea.

not-zip-safe

 Ditto.

PKG-INFO

 This is basically what we already have in .release_data().

SOURCES.txt

 I don't know the purpose of this file. It's a manifest of
 source files. The setuptools docs say it's not used anywhere.

top_level.txt

 This file just lists the top-level package names made available
 by the package. We could add a meta-data field for this
 information or use the "Provides:" field for it.

namespace_packages.txt

 This file lists the namespace packages used by the package. We
 could add a meta-data field for this or just use the "Requires:"
 field for it.

>> Additionally, it would make sense to have this data around
>> as static file for the PyPI mirrors to pick up.
> 
> 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.

If you look at the above mess of upper- and lower-case filenames,
files which only serve as marker and others having actual
content, different content types, etc. I think it's clear
that using this particular format is not a good idea.

We can do better :-)

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Sep 20 2010)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/


More information about the Catalog-SIG mailing list