3
Updating pip in a FUSE cryptomator vault breaks venv (sh.itjust.works)
submitted 1 month ago by DevCuber@sh.itjust.works to c/pythonhelp@lemmy.world
2 comments fedilink hide all child comments

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.

Here are the logs

  • 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 ?

you are viewing a single comment's thread
view the rest of the comments
[-] eager_eagle@lemmy.world 1 points 1 month ago* (last edited 1 month ago)

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.

[-] DevCuber@sh.itjust.works 1 points 1 month ago

Well I develop as a hobby and I'm fairly bad at it so I probably do a lot of stupid things but the reason I do it is because I sync my files using dropbox and don't want them to see those files (They might encrypt them but since it's closed source you can't know for sure)

this post was submitted on 24 Oct 2024
3 points (100.0% liked)

pythonhelp

562 readers
1 users here now

A community for posts that include helping Python programmers

Discord:
https://discord.gg/39K88eCxxr

founded 1 year ago
MODERATORS
Torro@lemmy.world