Re: [Distutils] Best way to handle packaging a project that only applies to certain versions of Python

All of this seems like too much worry for a project that only applies to Python 2.6 and earlier or Python 3.0. :) Thanks for the suggestions everyone, but I'm just going to let the folks stuck on legacy versions deal with the lack of wheels. On Mon, 29 Aug 2016 at 23:21 Thomas Kluyver wrote: > T

Re: [Distutils] Best way to handle packaging a project that only applies to certain versions of Python

There is also the 'python requires' metadata, which can now be provided via setuptools, but I think pip 8.2 needs to be released before that is respected. On Tue, Aug 30, 2016, at 01:08 AM, Daniel Holth wrote: > Let's say you have different code for python 3.3 and python 3.4+. Tag > one wheel py3

Re: [Distutils] Best way to handle packaging a project that only applies to certain versions of Python

Let's say you have different code for python 3.3 and python 3.4+. Tag one wheel py33-none-any and the second py34-none-any. The second wheel is preferred on python 3.4 and above, but ignored by 3.3. The py3 tag wouldn't work well here. Order of preference on 3.5 is: ('py35', 'none', 'any'), ('py3'

Re: [Distutils] Best way to handle packaging a project that only applies to certain versions of Python

> On Aug 29, 2016, at 7:34 PM, Brett Cannon wrote: > > Someone has asked that I do a new release of importlib that includes a > LICENSE file on PyPI: https://pypi.org/project/importlib/ > . Historically I have had the setup.py > simply not include any Pyth

[Distutils] Best way to handle packaging a project that only applies to certain versions of Python

Someone has asked that I do a new release of importlib that includes a LICENSE file on PyPI: https://pypi.org/project/importlib/. Historically I have had the setup.py simply not include any Python code when built on versions of Python that include importlib in the stdlib itself: https://github.com/