Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Nathaniel Smith
On Thu, Jun 15, 2017 at 7:58 PM, Donald Stufft wrote: > > On Jun 15, 2017, at 10:51 PM, Nathaniel Smith wrote: > > I can see some benefit to standardizing on a single format instead of > making every backend author learn e.g. the weird quirks required to > get

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Daniel Holth
The format you want is zstandard or brotli. Maybe fastly be interested in sponsoring bandwidth efficient file formats? :-) It would be cool to have a way to do signatures and hashing before compression. On Thu, Jun 15, 2017, 22:59 Donald Stufft wrote: > > On Jun 15, 2017, at

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Donald Stufft
> On Jun 15, 2017, at 10:51 PM, Nathaniel Smith wrote: > > I can see some benefit to standardizing on a single format instead of > making every backend author learn e.g. the weird quirks required to > get unicode filenames correct in two different formats, and I'm not > sure why

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Nathaniel Smith
On Thu, Jun 15, 2017 at 1:55 PM, Brett Cannon wrote: > Then shouldn't we be pushing for .tar.xz instead? (The Rust community is > actually moving to .tar.xz for distributing Rust itself: > https://users.rust-lang.org/t/rustup-1-4-0-released/11268 ; I don't know > what their

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Donald Stufft
> On Jun 15, 2017, at 5:05 PM, Paul Moore wrote: > > On 15 June 2017 at 21:49, Daniel Holth wrote: >> Nothing wrong with sdist of course, but one thing I hear from the emphasis >> on sdist (something that pip can build automatically) is that maybe we are

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Donald Stufft
> On Jun 15, 2017, at 4:55 PM, Brett Cannon wrote: > > > > On Thu, 15 Jun 2017 at 08:25 Donald Stufft > wrote: > >> On Jun 15, 2017, at 10:10 AM, C Anthony Risinger >

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Donald Stufft
> On Jun 15, 2017, at 4:29 PM, Nathaniel Smith wrote: > > - However, I am more dubious about hacking stuff like prepare_build_files > into the standard to support this specific interaction between two specific > tools, especially since it's not at all obvious to me that this

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Brett Cannon
On Thu, 15 Jun 2017 at 08:25 Donald Stufft wrote: > > On Jun 15, 2017, at 10:10 AM, C Anthony Risinger > wrote: > > On Tue, Jun 13, 2017 at 8:53 PM, Nick Coghlan wrote: > >> On 13 June 2017 at 19:44, Thomas Kluyver

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Paul Moore
On 15 June 2017 at 21:49, Daniel Holth wrote: > Nothing wrong with sdist of course, but one thing I hear from the emphasis > on sdist (something that pip can build automatically) is that maybe we are > worried that a publisher, who gave us the software for free, will unduly >

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Daniel Holth
Nothing wrong with sdist of course, but one thing I hear from the emphasis on sdist (something that pip can build automatically) is that maybe we are worried that a publisher, who gave us the software for free, will unduly inconvenience the consumer. But that would require an obligation from the

Re: [Distutils] Finishing up PEP 517

2017-06-15 Thread Nathaniel Smith
On Thu, Jun 15, 2017 at 6:12 AM, Thomas Kluyver wrote: > Yes, it's PEP 517 again! Here's the current text: > > https://www.python.org/dev/peps/pep-0517/ > > We currently say: > >> All other hooks [except get_build_requires] are executed in an environment >> which contains

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Nathaniel Smith
On Wed, Jun 14, 2017 at 1:49 PM, Donald Stufft wrote: > > > On Jun 12, 2017, at 9:27 PM, Nick Coghlan wrote: > > > 5) Drop the prepare_files hook > Rationale: it's purpose is somewhat unclear at this point, and it > gives up the main advantage of going

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Donald Stufft
> On Jun 15, 2017, at 10:10 AM, C Anthony Risinger > wrote: > > On Tue, Jun 13, 2017 at 8:53 PM, Nick Coghlan > wrote: > On 13 June 2017 at 19:44, Thomas Kluyver >

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread C Anthony Risinger
On Tue, Jun 13, 2017 at 8:53 PM, Nick Coghlan wrote: > On 13 June 2017 at 19:44, Thomas Kluyver wrote: > > On Tue, Jun 13, 2017, at 02:27 AM, Nick Coghlan wrote: > > > I've updated the PR to specify zip archives for build_wheel and .tar.gz > > archives

Re: [Distutils] PEP 517: Open questions around artifact export directories

2017-06-15 Thread Thomas Kluyver
On Thu, Jun 15, 2017, at 03:10 PM, C Anthony Risinger wrote: > I'm not trying to open a bikeshedding opportunity here -- and I tried > to ignore it, honest! -- but why are tarballs preferable to zipfiles > for sdists?> > ... > > Just seems a little odd/arbitrary to me that wheel is zip, python >

[Distutils] Finishing up PEP 517

2017-06-15 Thread Thomas Kluyver
Yes, it's PEP 517 again! Here's the current text: https://www.python.org/dev/peps/pep-0517/ We currently say: > All other hooks [except get_build_requires] are executed in an environment > which contains both the bootstrap requirements specified in the > pyproject.toml hook and those