-
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
Installing several libs to the same target can result in an exception #1356
Comments
I agree, this copy needs to filter out pycache. |
That approach appears to work on python3 (tested with
'.../python_modules/coverage/coverage' already exists |
Two possible solutions would be to either;
I'm happy to implement either of the first two, however I suspect someone with greater knowledge of |
I'm hit with this one - pressing deadline at the moment so I'm just going to work around, but I'll try to come back and submit a pull request soon. I'm assuming no one else has tried anything since Feb? |
/cc @qwcode As of #2122 (v6.0) this issue changed, but still exists:
It can now be mitigated more easily by simply always using the As previously stated, I'm happy to spend a bit of time on this, but would appreciate some guidance as to what desired behaviour would be, and where that logic should live in advance of committing time and effort to a solution that may ultimately be unacceptable in the context of the broader community. |
Closing this. It currently works fine, but you do get some warnings due to already existing files and not wanting to upgrade those files without a |
Steps to produce:
Result:
Wrapping this line in a
try..except
solves this problem for me, not sure how viable that is as a real world fix.Guessing this occurs because each tries to move the
__pycache__
folder. The first two succeed (sort of; the second__pycache__
ends up inside the first), the third fails. Another solution might be to exempt__pycache__
from being copied here?The text was updated successfully, but these errors were encountered: