Writing ~/.pydistutils.cfg affects parallel builds. about shiv HOT 9 CLOSED

How about checking for the presence of the incompatible prefix option in pydistutils, and stop with an error message, prompting the user to pass an additional shiv command line option to enable the trick?

from shiv.

cc @rouge8

from shiv.

I would say go for whichever you think is the more important use case. I think pypa/pip#4557 is the upstream pip issue which looks like it's back to life and will hopefully make it into the next pip release 🤞

from shiv.

Does --no-user-cfg work for this problem?

Relevant issues upstream:

• https://bugs.python.org/issue1180
• https://bugs.python.org/issue34389

from shiv.

@warsaw only for source dists, not for wheels :(

from shiv.

Well, that's unfortunate. It won't help right away, but we should look into fixing this upstream.

from shiv.

It gets worse though, even without an enterprise build system.

Here's a simple experiment that proves how broken this is.
Build something with shiv (project A) in one terminal session and in another build another app that does not use shiv (project B) -- at the same time. For example start commands one after the other. The project B build will break because of the custom ~/.pydistutils.cfg stored during its build from project A build.

This proves that changing shared distutils settings in ~/pydistutils.cfg is not an acceptable solution at all, under any circumstances. If the build is going to change distutils settings at all, it must do that local to the project built by shiv only.

Thus, as I suggested, let's revert this bug, to get a good release, and than carefully plan a workaround for homebrew Python users that is localized to one project build.

from shiv.

@zvezdan I agree, thanks for clarifying the scope

from shiv.

reverted in #50

from shiv.