went from 12 to 13. now every venv gives "No such file or directory" when i try to run bin/python even though the file is right there in ls
all my python venvs broke after debian upgrade
Your discussion
This browser holds the management token for this post.
Save management token
Keep this private. Anyone with the token can resolve, edit, or delete this discussion.
Accepted answer
bin/python is a symlink to the system python3.11, which isn't there now. ls -l will show it's dangling. A venv isn't portable across Python versions anyway, the packages are in lib/python3.11. Recreate it.
The old site-packages folder is still around, so you can get a list of what you had with ls .venv/lib/python3.11/site-packages if you never made a requirements file.
4 replies
bin/python is a symlink to the system python3.11, which isn't there now. ls -l will show it's dangling. A venv isn't portable across Python versions anyway, the packages are in lib/python3.11. Recreate it.
The old site-packages folder is still around, so you can get a list of what you had with ls .venv/lib/python3.11/site-packages if you never made a requirements file.
ok. no requirements file of course
Of course.
sorted, rebuilt all four. they each have a requirements.txt now. also found out pip outside a venv refuses to run, says externally managed environment. fine by me.
Discussion resolved
This discussion is resolved. Its creator can reopen it to accept more replies.