Re: [Distutils] multiple backports of ipaddress and a world of pain

2016-02-18 Thread Chris Withers
Hi Nick, On 18/02/2016 13:32, Nick Coghlan wrote: On 17 February 2016 at 04:37, Chris Withers wrote: So, RHEL7, for worse or worse, ships with Python 2.7.5.

Re: [Distutils] PEP 516 and pypa.json

2016-02-18 Thread Ethan Furman
On 02/18/2016 12:00 PM, Daniel Holth wrote: > On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote: >> I saw PEP-0516 go through check-ins, and had a question about the >> pypa.json portion of the proposal -- namely, why are we using a >> .json file? >> >> I presume this is a file that will be

Re: [Distutils] PEP 516 and pypa.json

2016-02-18 Thread Daniel Holth
I'm still pulling for RFC 822 format :) On Thu, Feb 18, 2016, 14:33 Nathaniel Smith wrote: > On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote: > > Greetings! > > > > I saw PEP-0516 go through check-ins, and had a question about the > pypa.json > > portion

Re: [Distutils] PEP 516 and pypa.json

2016-02-18 Thread Nathaniel Smith
On Thu, Feb 18, 2016 at 9:06 AM, Ethan Furman wrote: > Greetings! > > I saw PEP-0516 go through check-ins, and had a question about the pypa.json > portion of the proposal -- namely, why are we using a .json file? > > I presume this is a file that will be created by hand, and

[Distutils] PEP 516 and pypa.json

2016-02-18 Thread Ethan Furman
Greetings! I saw PEP-0516 go through check-ins, and had a question about the pypa.json portion of the proposal -- namely, why are we using a .json file? I presume this is a file that will be created by hand, and while json is not as ugly as xml, it's certainly not pretty. Can we not use an

Re: [Distutils] abstract build system PEP update

2016-02-18 Thread Paul Moore
On 18 February 2016 at 13:48, Nick Coghlan wrote: >> Yes, twine is a good, concrete example. > > I believe tools like pyp2rpm, conda skeleton, py2dsc and fpm also rely on > that static sdist metadata (I'm not 100% sure on that, but it would make > sense for them to do so).

Re: [Distutils] abstract build system PEP update

2016-02-18 Thread Daniel Holth
Yes PKG-INFO is reasonably useful and easy to hand-edit. It would be easy to maintain. If you were doing it manually the only thing you would need to update frequently would be the version number. On Thu, Feb 18, 2016 at 8:48 AM Nick Coghlan wrote: > On 18 February 2016 at

Re: [Distutils] abstract build system PEP update

2016-02-18 Thread Nick Coghlan
On 18 February 2016 at 07:30, Paul Moore wrote: > On 17 February 2016 at 21:01, Nathaniel Smith wrote: > > On Feb 17, 2016 4:44 AM, "Donald Stufft" wrote: > >> > > [...] > >> You could say that using twine to handle the uploading is a

Re: [Distutils] multiple backports of ipaddress and a world of pain

2016-02-18 Thread Nick Coghlan
On 17 February 2016 at 04:37, Chris Withers wrote: > Hi All, > > (Apologies for copying in the maintainers of the two backports and > django-netfields directly, I'm not sure you're on this distutils list...) > > This is painful and horrible, and I wish pip would prevent >

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

2016-02-18 Thread Olivier Grisel
Strong +1 for all Donald's proposals. -- Olivier ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] abstract build system PEP update

2016-02-18 Thread Donald Stufft
> On Feb 18, 2016, at 5:26 AM, Paul Moore wrote: > > [1] One downsides of managing PEPs as PRs against the packaging specs > is that there is no easy quotable term to refer to them by - we could, > and probably should, use the PR number. And as a consequence, it's > hard to

Re: [Distutils] abstract build system PEP update

2016-02-18 Thread Paul Moore
On 17 February 2016 at 22:58, Robert Collins wrote: >> The latter option is far easier (we're basically almost there) but it >> will *not* suit build tools that can't (or won't) generate a sdist >> that conforms to PEP 314 (i.e., contains PKG-INFO). > > I still don't