What you would do is put your project in src/ and choose a build system that allows the same, if you happen to be developing such a conflicting project.
On Sat, Jul 29, 2017 at 1:29 PM Paul Moore <p.f.mo...@gmail.com> wrote: > On 29 July 2017 at 17:46, Nathaniel Smith <n...@pobox.com> wrote: > > So one consequence of this is that every time a new release of flit (for > > example) adds a new dependency on X, or one of flit's dependencies adds a > > new dependency on X, then this is technically a backwards incompatible > > change, because any existing packages that use flit and happen to have a > top > > level directory named X will stop working. > [...] > > Or am I worrying about a non-issue and it's fine if flit imports click > from > > the source tree? > > This sounds like a pretty rare issue, and one that I'd be inclined to > assume isn't going to be a problem in practice - but if it were > considered worth worrying about, why not just put the project root at > the *end* of sys.path, so that packages installed normally will take > precendence? > > Paul > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
