[Distutils] Fwd: Fwd: Re: PEP 517 again

xoviat xoviat at gmail.com
Thu Aug 24 15:26:10 EDT 2017

---------- Forwarded message ----------
From: xoviat <xoviat at gmail.com>
Date: 2017-08-24 14:26 GMT-05:00
Subject: Re: [Distutils] Fwd: Re: PEP 517 again
To: Thomas Kluyver <thomas at kluyver.me.uk>

And also, are Nick and Paul okay with this?

2017-08-24 14:24 GMT-05:00 xoviat <xoviat at gmail.com>:

> So in summary:
> - NotImplementedError
> - Remove build_dir and specify that no modifications can be made to the
> source directory
> On the third issue:
> I understand where Nathaniel is coming from in regards to sys.path. But
> there should at least be an option for this because of for example, numpy:
> numpy builds itself with it's own build system that is defined in the
> source directory. If you remove '' from sys.path, then numpy cannot build
> itself because there is no other numpy.distutils package.
> 2017-08-24 14:00 GMT-05:00 Thomas Kluyver <thomas at kluyver.me.uk>:
>> On Thu, Aug 24, 2017, at 07:30 PM, Leonardo Rochael Almeida wrote:
>> It looks like a lot of trouble for a feature that is designed to solve a
>> problem for a very thin intersection of the Venn diagram of people who:
>>  a. wants to quickly iterate while hacking a package
>>  b. doesn't want to bother learning how to trigger the incremental build
>> system of that package or how to install it in editable mode.
>> For better or worse, editable installs exist and don't need to be defined
>> by PEP 517 just to handle this case. I'm not convinced it's worth the
>> additional complexity of the spec just for that.
>> This is a good point. Given that developers can use the build tool
>> directly for development purposes, rather than going through the PEP 517
>> interface, we don't need to prioritise that use case for the spec.
>> So for the time being, I'd prefer to say that the build_wheel() hook
>> should not create or modify files in the source directory. Backends may
>> keep their own caches elsewhere to speed up repeated builds, but any more
>> provisions for developer use cases should be left for a future PEP. And
>> developers can invoke enscons/flit/... directly in the meantime.
>> _______________________________________________
>> Distutils-SIG maillist  -  Distutils-SIG at python.org
>> https://mail.python.org/mailman/listinfo/distutils-sig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20170824/4286ebe0/attachment-0001.html>

More information about the Distutils-SIG mailing list