On Tue, Aug 22, 2017 at 9:23 AM, Daniel Holth <dholth@gmail.com> wrote:
Isn't this a special case of needing . on sys.path when building a package? Then the same version of setuptools that is being packaged builds itself.
No. The issue for us it wasn't setuptools itself, but it's dependencies and those dependencies conflicted with dependencies of of packages we were installing *and* those packages importing these dependences (indirectly) in their setup scripts. Setup scripts that import the thing they're about to install, generally to get the version :(, is something I'd love to see go away.