You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After 3153 and related PRs were merged I noticed the warnings about "egg_info for package X produced metadata for project name Y Fix your #eggfragments." but as it was only a warning I didn't delve into it at the time.
I've just discovered that packages with this warning don't uninstall - I have to manually delete remnants from src and site-packages. This is going to be a pain as it requires manually going through deployments to about 20 separate websites.
Now - my workaround wasn't documented and was probably incorrect - but I'm creating an issue just in case I wasn't alone in this and in case it is useful to the pip developers. If it's a case of "you shouldn't have done something so dumb" then feel free to close the ticket.
The text was updated successfully, but these errors were encountered:
Related to: #3153
Last year I discovered that if my requirements.txt installs were from git branches:
then I changed the branch:
then a pip install -U failed to work correctly (apologies - I can't remember exactly what failed)
After a lot of hair pulling I figured out the fix (for me at least) was to ensure I always updated the egg name:
and
After 3153 and related PRs were merged I noticed the warnings about "egg_info for package X produced metadata for project name Y Fix your #eggfragments." but as it was only a warning I didn't delve into it at the time.
I've just discovered that packages with this warning don't uninstall - I have to manually delete remnants from src and site-packages. This is going to be a pain as it requires manually going through deployments to about 20 separate websites.
Now - my workaround wasn't documented and was probably incorrect - but I'm creating an issue just in case I wasn't alone in this and in case it is useful to the pip developers. If it's a case of "you shouldn't have done something so dumb" then feel free to close the ticket.
The text was updated successfully, but these errors were encountered: