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
TLDR: if you're having problems with corrupt pip/setuptools, then delete ~/. local/share/virtualenv
I tried to install a new environment today and ran into a lot of weird import errors from pip. I quite soon realised that the cached version of pip was corrupted and it couldn't even import to run a poetry install/update command. Reading #732 taught me that poetry uses virtualenv to initialise environments with pip and setuptools before performing any further operations.
I'm posting this issue for documentation reasons rather than in order to fix the original error. I searched quite hard on the issues and the documentation but didn't find any reference to this cache (in the end I ran poetry -vvv install which printed where it was retrieving virtualenv from).
It would be really useful if there could be some documentation of where the various caches are stored for poetry, they are often the source of "sudden weird bugs". The three caches I can find documented here are config, data, and cache. Only the cache is listed by poetry config --list, and only the data directory is mentioned in the uninstall guide.
It would be nice if the source of virtualenv could also be listed there, I'm sure it's a common debugging route.
I also find it a bit inconsistent to suggest only deleting the "data" folder and not the other ones in the uninstall guide, but not essential.
Description
TLDR: if you're having problems with corrupt pip/setuptools, then delete
~/. local/share/virtualenv
I tried to install a new environment today and ran into a lot of weird import errors from pip. I quite soon realised that the cached version of pip was corrupted and it couldn't even import to run a poetry install/update command. Reading #732 taught me that poetry uses
virtualenv
to initialise environments withpip
andsetuptools
before performing any further operations.I'm posting this issue for documentation reasons rather than in order to fix the original error. I searched quite hard on the issues and the documentation but didn't find any reference to this cache (in the end I ran
poetry -vvv install
which printed where it was retrievingvirtualenv
from).It would be really useful if there could be some documentation of where the various caches are stored for poetry, they are often the source of "sudden weird bugs". The three caches I can find documented here are config, data, and cache. Only the cache is listed by
poetry config --list
, and only the data directory is mentioned in the uninstall guide.It would be nice if the source of
virtualenv
could also be listed there, I'm sure it's a common debugging route.I also find it a bit inconsistent to suggest only deleting the "data" folder and not the other ones in the uninstall guide, but not essential.
Thanks for your help.
Workarounds
Just delete all caches :)
Poetry Installation Method
other
Operating System
(WSL) Ubuntu 22.04.03
Poetry Version
1.8.3
Poetry Configuration
Python Sysconfig
No response
Example pyproject.toml
No response
Poetry Runtime Logs
where the last line indicates the virtualenv cache location
The text was updated successfully, but these errors were encountered: