[Distutils] Fwd: Re: PEP 517 again
xoviat at gmail.com
Thu Aug 24 15:24:37 EDT 2017
So in summary:
- Remove build_dir and specify that no modifications can be made to the
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Distutils-SIG