{"thread":{"id":"Bfbb_vpFmO91","title":"all my python venvs broke after debian upgrade","content":"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","category":"help","status":"resolved","author":"mo","createdAt":"2026-10-14T19:54:14.234Z","updatedAt":"2026-10-15T00:54:14.234Z","expiresAt":null,"replyCount":4},"replies":[{"id":"4krjKsWnwHPO","content":"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.\n\nThe 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.","author":"oldpc","createdAt":"2026-10-14T20:14:14.234Z"},{"id":"Q0t4NOaJta5q","content":"ok. no requirements file of course","author":"mo","createdAt":"2026-10-14T20:59:14.234Z"},{"id":"vDTbjtaFXTGi","content":"Of course.","author":"lintroller","createdAt":"2026-10-14T21:14:14.234Z"},{"id":"VjceLIsSGesi","content":"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.","author":"mo","createdAt":"2026-10-15T00:54:14.234Z"}]}