[Distutils] What are reasonable compatibility tags? (was: Three clarification questions about PEP 425 and PyPy3

On Fri, 31 Aug 2018 at 01:41 Paul Moore wrote: > On Fri, 31 Aug 2018 at 07:15, Nathaniel Smith wrote: > > > > On Thu, Aug 30, 2018 at 6:52 PM, Brett Cannon wrote: > > > > > > > > > On Thu, 30 Aug 2018 at 11:21 Nathaniel Smith wrote: > > > >> * Make the 3 tag categories totally independent.

[Distutils] Re: What are reasonable compatibility tags? (was: Three clarification questions about PEP 425 and PyPy3

Le ven. 31 août 2018 à 9:25 PM, Brett Cannon a écrit : > > OK, so let's look at what we're trying to support. If we have pure Python > code there's very likely going to be a bottom Python version that's > supported and then forward-compatibility is assumed. This is specified > today through

[Distutils] Re: What are reasonable compatibility tags? (was: Three clarification questions about PEP 425 and PyPy3

On Fri, 31 Aug 2018 at 13:33 Xavier Fernandez wrote: > > > > Le ven. 31 août 2018 à 9:25 PM, Brett Cannon a écrit : > >> >> OK, so let's look at what we're trying to support. If we have pure Python >> code there's very likely going to be a bottom Python version that's >> supported and then

[Distutils] Re: Three clarification questions about PEP 425 and PyPy3

On Thu, 30 Aug 2018 at 23:13 Nathaniel Smith wrote: > On Thu, Aug 30, 2018 at 6:52 PM, Brett Cannon wrote: > > > > > > On Thu, 30 Aug 2018 at 11:21 Nathaniel Smith wrote: > >> > >> If we're going to rethink this, > > > > > > Well, I didn't want to "rethink" so much as "fill in". :) > > > >> >

[Distutils] Environment markers for GPU/CUDA availibility

Hi all, trying to pull together a few separate discussions into a single thread here. The main issue is that currently PEP 508 does not provide environment markers for GPU/CUDA availability, which leads to problems for projects that want to provide distributions for environments with and without

[Distutils] Re: Environment markers for GPU/CUDA availibility

I’m not knowledgable about GPUs, but from limited conversations with others, it is important to first decide what exactly the problem area is. Unlike currently available environment markers, there’s currently not a very reliable way to programmatically determine even if there is a GPU, let alone

[Distutils] Re: Three clarification questions about PEP 425 and PyPy3

> On Aug 30, 2018, at 9:54 PM, Brett Cannon wrote: > > I initially thought 'packaging', but I also don't want to care about Python > 2. :) So I haven't decided yet. At worst this just leads to a clearer > understanding of how tools should do wheel compatibility matching. If you want to get

[Distutils] Re: Three clarification questions about PEP 425 and PyPy3

On Thu, Aug 30, 2018 at 6:52 PM, Brett Cannon wrote: > > > On Thu, 30 Aug 2018 at 11:21 Nathaniel Smith wrote: >> >> If we're going to rethink this, > > > Well, I didn't want to "rethink" so much as "fill in". :) > >> >> then I would really like to move away from assigning special meaning to >>

[Distutils] Re: Three clarification questions about PEP 425 and PyPy3

On Fri, 31 Aug 2018 at 07:15, Nathaniel Smith wrote: > > On Thu, Aug 30, 2018 at 6:52 PM, Brett Cannon wrote: > > > > > > On Thu, 30 Aug 2018 at 11:21 Nathaniel Smith wrote: > >> * Make the 3 tag categories totally independent. Compute a separate set > >> for each, and then take the full cross

[Distutils] Editable requirement parsing in pip

Hi, I was verifying my Pipenv resolver work, and found a quirk in pip when handling -e requirements. With a requirements.txt: # Works as expected colorama ; os_name == "nt" # Works as expected ./colorama ; os_name == "nt" # Drops markers; always installs disregarding the