[Catalog-sig] API search by python version (or classifier)

Jannis Leidel jannis at leidel.info
Thu Jan 27 16:23:42 CET 2011

On 27.01.2011, at 15:07, Tarek Ziadé wrote:

> On Thu, Jan 27, 2011 at 11:38 AM, Jannis Leidel <jannis at leidel.info> wrote:
>> On 27.01.2011, at 09:34, Tarek Ziadé wrote:
>>> Oh... so what about this:
>>> - PyPI publishes setuptools metadata, but in Metadata 1.2 format. The
>>> conversion is pretty simple, it's just translating the requires.txt
>>> into PEP 345 fields.
>>> - We add a marker so we know that those metadata are from setuptools
>>> That way, PyPI has an unified interface to get the dependencies, and
>>> if there's an issue in project X because the static metadata fails on
>>> platform Y, we ask the project to provide real PEP 345 metadata.
>> How would the last bit work?
> By providing a [metadata] section in your setup.cfg that contains them.
> The idea is that a project can provide a compatibility for d2 without
> removing the one for d1 - so pip and easy_install still work :
> - d1/setuptools/distribute : setup.py
> - d2: setup.cfg
> Then, by using distutils2 register command, you can push the Metadata
> 1.2 to pypi.
> This week end we're having a sprint where we will document this
> process. We're also planning to provide a script to
> automate the creation of [metadata] by running setup.py to make it easier.

Sounds great, +1.


More information about the Catalog-SIG mailing list