cross-posted from: https://sh.itjust.works/post/27097438
I store my programs in a cryptomator vault which uses a fuse virtual drive (The default on Linux), but when trying to update pip inside a venv I get an error, then any subsequent use of pip also throws an error and {path_to_venv}/lib/python3.12/site-packages/pip/ becomes empty.
I imagine this is an issue that would happen in any FUSE drive although I don’t know how to test that.
- OS : Fedora 40
- pip version: 23.3.2 updating to 24.2
- python version: 3.12.7
I already made a bug report on the github
Does anyone know a temporary workaround for this ?
I don’t have a solution, but I’m wondering why one would develop in a Cryptomator vault.
I’ve had my share of issues with access to files in Cryptomator degrade over time and being unable to unmount the volume properly. IME it doesn’t work well for frequently modified files, or several smaller ones like you have in .venv and node_modules.
