A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2008-October/082851.html below:

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

[Python-Dev] 3.1 focus (was Re: for __future__ import planning) [Python-Dev] 3.1 focus (was Re: for __future__ import planning)"Martin v. Löwis" martin at v.loewis.de
Sun Oct 5 06:59:36 CEST 2008
> 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.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4