[Catalog-sig] [Python-Dev] egg_info in PyPI
mal at egenix.com
Sat Sep 18 23:09:35 CEST 2010
"Martin v. Löwis" wrote:
>> So you are fine with publishing "slightly incorrect" metadata at PyPI
>> ? I am not.
> I really have no intuition for in how many cases the data will be
> incorrect. However, if users find that the data is incorrect for
> specific package, they ought to complain to the maintainer.
>> I don't understand the rational behind providing flawed data at PyPI.
>> I am -1 on that.
> -1 sounds much better than vetoing it :-) Taking the votes together,
> I currently arrive at
> Tarek -1
> Michael -1 (?)
> Jannis -1 (?)
> Jim +1
> Thomas +1
> Any other opinions?
-1 as well. The formats and file-names are just a complete mess and
not all packages on PyPI are available as eggs or compatible to
I think the information from PEP 345 which is already made
available via the XML-RPC .release_data() interface is sufficient
for most cases. In those cases where it is not, we should extend the
It may be worthwhile providing the same sort of information as static
PKG-INFO file alongside the /simple index entries as well (e.g.
via a link on the package page), to make it possible to extract
the meta information without having to use the RPC mechanism
and making use of the mirror infrastructure.
PS: Could you put your DZUG talk up online somewhere. It includes
some very valuable information on the various available APIs that
is difficult to find elswhere.
Professional Python Services directly from the Source (#1, Sep 18 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
More information about the Catalog-SIG