Re: [Distutils] Idea: Using Trove classifiers for platform compatibility warnings

2017-04-24 Thread Thomas Kluyver
On Sat, Apr 8, 2017, at 03:17 AM, Nick Coghlan wrote: > 2. At least one "Programming Language :: Python" tag is set, but the > tags don't include any that cover the *current* Python version We've just enabled setuptools, PyPI and pip to use the python-requires metadata field, so that (for

Re: [Distutils] Idea: Using Trove classifiers for platform compatibility warnings

2017-04-08 Thread Nick Coghlan
On 8 April 2017 at 19:29, Paul Moore wrote: > On 8 April 2017 at 03:17, Nick Coghlan wrote: >> The "at least one relevant tag is set" pre-requisite would be to avoid >> emitting false positives for projects that don't provide any platform >> compatibility

Re: [Distutils] Idea: Using Trove classifiers for platform compatibility warnings

2017-04-08 Thread Paul Moore
On 8 April 2017 at 03:17, Nick Coghlan wrote: > PyPI already has a reasonably extensive component tagging system in > https://pypi.python.org/pypi?%3Aaction=list_classifiers but we don't > really *use* it all that much for programmatic purposes. > > That means the incentives

[Distutils] Idea: Using Trove classifiers for platform compatibility warnings

2017-04-07 Thread Nick Coghlan
PyPI already has a reasonably extensive component tagging system in https://pypi.python.org/pypi?%3Aaction=list_classifiers but we don't really *use* it all that much for programmatic purposes. That means the incentives for setting tags correctly are weak, since there isn't much pay-off in the