• update some packages • python development with venv breaks again JUST
Then there's virtualenvwrapper, virtualenvwrapper.el, uv-virtualenvwrapper, uv-virtualenvrapper.el
Someone should build a wrapper for these 🥁
The python experience
So true
Darn Python eats my brain every single time I have to do anything that involves dealing with more than five lines of code. The fragmentation is just not even funny anymore - virtualenv, venv, pipenv, poetry, conda, including tools like mise, and that's just to deal with environment. Add to that, path management complexity; shell integration challenges; no project isolation; IDE integration woes, etc. And you know what? Maybe we should celebrate that. Fuck it, if there always be opportunities to unmess some Python crap, rewriting stuff in babashka, why should we even tell them something's wrong with it? Enter a new era - vibe-coded Python tar pits. Who's still worried AI will take their jobs?
------- and btw. do try https://mise.jdx.dev/ it handles venv nicely, you just need a mise.toml with:
[env]
_.python.venv = { path = ".venv", create = true }
and of course, there's mise.el for Emacs. Works even for Eshell.I write Python daily (work), and quite often during off-hours too (open source) 👴 . Let me know if I can help!