-
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 packages with different egg names fail in pip>=20.3 #9217
Comments
Hello and thank you for your bug report! I'm sorry you're having trouble right now. Thank you for sharing your report with us. Here's a list of some things to watch out for in the new version of pip, including some changes to how we deal with editable packages. I'll mention here one useful troubleshooting and workaround tip from the documentation: if you need a temporary workaround, you can choose the old resolver behavior using the flag (If you don't mind, please also tell us what could have happened differently so you could have tested and caught and reported this during the pip resolver beta period.) |
@uranusjr @pradyunsg An acquaintance of mine filed pypa/packaging-problems#428 and thought it might be related to this issue; is it? |
I believe the packaging-problems issue is a symptom of #9429. The new resolver requires URLs to match exactly, but the legacy |
Closing this out since:
|
Environment
Description
Since pip version 20.3, installing an editable package with a different #egg={name_different_than_pkg}, no longer works.
Expected behavior
This works fine for pip versions < 20.3.
How to Reproduce
For example:
Output
Verbose Output
The text was updated successfully, but these errors were encountered: