-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pip install -U . fails when there's a UNIX domain socket in the current directory #5306
Comments
A fix for this would be that pip tries to be smarter about what it's copying. Honestly though, I have a feeling that adding support for a Unrelated: pip will always reinstall from a local directory -- |
It's also arguably a bug in
|
(And thanks for the tip about not needing |
Thanks to @chrahunt and @cjerdonek, there's a Python-3-only fix for this which skips copying socket files when copying the source directory. 🎉 |
Description:
It seems pip 10.0.1, when installing from a directory, makes a copy of that directory before doing anything else (?). This causes problems for mypy developers. We have a daemon process that creates a UNIX domain socket named
dmypy.sock
in the current directory. When the mypy daemon is running in the mypy directory, and we try to install from there, this copy fails with the following error:Using
-v
we get the following traceback:A simple workaround is to stop the daemon (or if it's been killed,
rm dmypy.sock
).(First reported for mypy: python/mypy#4945, for @ilevkivsky.)
The text was updated successfully, but these errors were encountered: