| From: Stewart C. Russell via talk <talk@gtalug.org> | Did you accidentally install "python-is-python2"? It will break modern things | in a hilarious manner. | | There's python-is-python3 to undo the damage. Wow. The Python2 -> Python3 transition is still claiming victims! I am not sold on containers, but it sure is an argument for ONLY allowing Python2 in containers. Kind of like radioactive waste. Or maybe it is time to write off all Python2-only code. After all, official maintenance is over, even security maintenance. After 10 years, if I remember correctly. Contrast this with the C -> C++ transition. They can coexist. In fact, I personally program in C, not C++, and don't find problems caused by C++ being on my system. ============================ There's another thing that bothers me about Python (and a few other projects). I get almost all my software from my distro (Fedora Linux). But there are reasons to get things through Python's "pip". Surely these two sources clash. There is a similar problem with several rich ecosystems. For example Rust, Perl, TeX/LaTeX, ... In the background are the many issues of trust (eg. "supply chain attacks").