On 14 Dec. 2017 1:55 pm, "Donald Stufft" wrote:
Overall I’m +1, not sure if it would be a new PEP or an amendment to the
current PEPs but I think it’s a good idea.
It would be a new PEP bumping the metadata version to 1.4 (that will be
less tedious than it used to be though, since it will only
On 14.12.2017 5:25, Nathaniel Smith wrote:
On Wed, Dec 13, 2017 at 6:11 PM, Ivan Pozdeev via Distutils-SIG
wrote:
On 14.12.2017 3:17, Barry Warsaw wrote:
I'm about to release a new version of importlib_resources, so I want to
get my flit.ini's require-python clause right. We support Python
On 14.12.2017 5:25, Nathaniel Smith wrote:
On Wed, Dec 13, 2017 at 6:11 PM, Ivan Pozdeev via Distutils-SIG
wrote:
On 14.12.2017 3:17, Barry Warsaw wrote:
I'm about to release a new version of importlib_resources, so I want to
get my flit.ini's require-python clause right. We support Python
On Wed, Dec 13, 2017 at 6:11 PM, Ivan Pozdeev via Distutils-SIG
wrote:
>
>
> On 14.12.2017 3:17, Barry Warsaw wrote:
>>
>> I'm about to release a new version of importlib_resources, so I want to
>> get my flit.ini's require-python clause right. We support Python 2.7,
>> and 3.4 and beyond. This
On 14.12.2017 3:17, Barry Warsaw wrote:
I'm about to release a new version of importlib_resources, so I want to
get my flit.ini's require-python clause right. We support Python 2.7,
and 3.4 and beyond. This makes me sad:
requires-python = '>=2.7,!=3.0,!=3.1,!=3.2,!=3.3'
Of course, I'd like
On Dec 13, 2017, at 19:39, Dustin Ingram wrote:
>
> It seems like a small amount of convenience in exchange for a
> significant increase in complexity to me.
I can’t speak to the complexity, but it’s very definitely an important use
case. Imagine when Python 3.10 is out; do you really want to
> On Dec 13, 2017, at 7:17 PM, Barry Warsaw wrote:
>
> I understand that OR clauses aren't supported under any syntax
> currently, but as PEPs 566 and 508 are still open/active, wouldn't it be
> reasonable to support something like this explicitly?
I personally think this is a good idea, and i
It seems like a small amount of convenience in exchange for a
significant increase in complexity to me.
FYI, some previous discussion on the topic can be found here:
https://mail.python.org/pipermail/distutils-sig/2016-September/029651.html
And also here:
https://github.com/pypa/setuptools/
I'm about to release a new version of importlib_resources, so I want to
get my flit.ini's require-python clause right. We support Python 2.7,
and 3.4 and beyond. This makes me sad:
requires-python = '>=2.7,!=3.0,!=3.1,!=3.2,!=3.3'
Of course, I'd like to write this like:
requires-python = '(>=2
