alt Hacker News> Make sure you don't have anything else relying on Python because they will probably never work again.
This is why when I see some clever open source tool discussed on HN and I go to the repo and see it's written in Python I close the browser window and pretend I never saw it.
Yes I know there are ways to protect yourself when using Python in much the same way that lead-lined glove boxes protect you when working with plutonium, but I can never remember the proper CLI incantation to make the lead-lined glove box appear.
Replies
These kinds of histrionics are really uncalled for. Virtual environments are easy to work with. https://chriswarrick.com/blog/2018/09/04/python-virtual-envi... is a solid tutorial.
These days, if I'm feeling generous I'll spend a minute or two to see if I can get a promising Python tool to install with uv. If it's not going to easily submit to a `uv tool install`, then I move on and forget about it.
Is Python still that bad? I remember the big problems were during the Python 2 -> Python 3 transition, but in the last few years I've managed to get away with a single Python install and haven't really had any compatibility issues.
I stick with Python.org packages for macOS, and the official Python packages on Ubuntu, and everything seems to work just fine.
Ehm.. surely there are ecosystems making Python brilliant shiny in comparison.
Everybody else uses virtual environments and alternate installations of python instead of using and installing packages in the system python installation. It is not that hard.