[Python-Dev] 3.1 focus (was Re: for __future__ import planning)

Tarek Ziadé ziade.tarek at gmail.com
Sun Oct 5 10:25:49 CEST 2008

On Sun, Oct 5, 2008 at 6:59 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Setuptools declares dependencies, but does not add a Python version requirement,
>> like what was proposed in PEP 345 (http://www.python.org/dev/peps/pep-0345/)
>> with a new metadata called 'Requires Python'
>> Even if the problem is fixed in short term with a Trove classifier,
> Why would that be a short-term fix? It would work for the entire life
> time of Python 3, and can be easily extended for Python 4, so it sounds
> like a permanent solution to me.
> As a permanent solution, you need to keep the problem statement in mind,
> though: to allow people to determine whether a package works with Python 3.
>> the metadata of a package should provide this information imho.
> Well, the classifiers *are* part of the metadata of the package.

Yes and they are redundant to other metadata, like the licence for instance..

So maybe the problem is the other way: some specific metadata should be removed
since they are expressed in the classifier medatata. (e.g. only in one place)

There should be one-- and preferably only one --obvious way to do it.


More information about the Python-Dev mailing list