On 16 July 2017 at 00:15, Paul Moore <[email protected]> wrote: > On 15 July 2017 at 14:06, Thomas Kluyver <[email protected]> wrote: >> If those 'clutter' files are within the package directory (i.e. next to >> __init__.py), and we have to do a direct wheel build because VCS >> information is not available (not a VCS checkout, or VCS not on PATH), >> then I don't know how flit can avoid installing them, under any of the >> proposed isolation mechanisms. We can't extract a 'pristine' source tree >> from a non-pristine one without a list of what belongs in the pristine >> one - which flit gets from the VCS. > > Agreed. And I'm perfectly OK with a solution that reduces the odds of > issues rather than (futilely) trying to eliminate them totally, so I'm > happy to live with this.
Right, and the norms around what's reasonable and what's problematic will be resolved in the place where it makes sense to do so: between backend developers and their users. Frontend developers would only need to get involved *if* they see a pattern where *their* users are reporting problems, and those problems end up being consistently traced back to how a particular backend is handling requests for out-of-tree builds. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
