[Distutils] Re: Idea: perennial manylinux tag

2018-12-03 Thread Paul Moore
On Mon, 3 Dec 2018 at 15:30, Nick Coghlan wrote: > > On Mon, 3 Dec 2018 at 23:11, Paul Moore wrote: > > > > On Mon, 3 Dec 2018 at 12:16, Nick Coghlan wrote: > > > P.S. Paul asked how we can have manylinux tags without updating PEP > > > 425 to include them, and the answer is that the actual

[Distutils] Re: Idea: perennial manylinux tag

2018-12-03 Thread Nick Coghlan
On Mon, 3 Dec 2018 at 23:11, Paul Moore wrote: > > On Mon, 3 Dec 2018 at 12:16, Nick Coghlan wrote: > > P.S. Paul asked how we can have manylinux tags without updating PEP > > 425 to include them, and the answer is that the actual compatibility > > tag spec is at > >

[Distutils] Re: Idea: perennial manylinux tag

2018-12-03 Thread Paul Moore
On Mon, 3 Dec 2018 at 12:16, Nick Coghlan wrote: > P.S. Paul asked how we can have manylinux tags without updating PEP > 425 to include them, and the answer is that the actual compatibility > tag spec is at > https://packaging.python.org/specifications/platform-compatibility-tags/ > and that

[Distutils] Re: Idea: perennial manylinux tag

2018-12-03 Thread Nick Coghlan
On Fri, 30 Nov 2018 at 18:12, Nathaniel Smith wrote: > > We could do the Windows thing, and have a plain "manylinux" tag that means > "any recent-ish glibc-based Linux". Today it would be defined to be "any > distro newer than CentOS 6". When CentOS 6 goes out of service, we could > tweak the

[Distutils] Re: Idea: perennial manylinux tag

2018-12-03 Thread Matthew Brett
Hi, On Sat, Dec 1, 2018 at 5:18 PM Thomas Kluyver wrote: > > Thanks Nathaniel for the explanation. > > On Sat, Dec 1, 2018, at 4:39 AM, Nathaniel Smith wrote: > > So the proposal here is to refactor the spec to match how this > > actually works: the official definition of a manylinux_${glibc > >