Skip to content
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.

Do not overwrite files from already-installed packages #18

Closed
davidedelvento opened this issue Apr 2, 2020 · 2 comments
Closed

Do not overwrite files from already-installed packages #18

davidedelvento opened this issue Apr 2, 2020 · 2 comments

Comments

@davidedelvento
Copy link

Following the suggestion in pypa/pip#988 (comment) I am submitting this test case here.

Instead of just repeating myself, the issue is pypa/pip#4625

Not sure if that is in scope with the new dependency resolver, but mentioning it and let you think about it for a moment can't hurt.

@davidedelvento
Copy link
Author

This and #17 are two different things. This one is the most serious and is about pip silently overwriting files from previous packages it installed. In brief, if two unrelated packages a and b both have a foo.py file, in some circumstances (see pypa/pip#4625 for details) the second that gets installed overwrites the first, and pip does not notice.

Again, I am not sure if solving the issue is in the scope of what you are working on at the moment, but...

@pradyunsg pradyunsg reopened this Apr 4, 2020
@pradyunsg pradyunsg changed the title Verify that the new PIP does not overwrites files from other packages it installed Do not overwrite files from already-installed packages Apr 4, 2020
@pradyunsg
Copy link
Owner

Okay, I closed this for the wrong reasons earlier. However, this is not in scope for this project and is the same request as pypa/pip#4625.

I'm going to go ahead and close this in favor of that issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants