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@python.org https://mail.python.org/mailman/listinfo/distutils-sig
