Re:Escaping from Anaconda's Stranglehold on macOS
by rbanffy on Sunday September 01, 2024 @06:43PM
(#41421020)
You won’t break a machine by installing Python packages on an OS that never uses Python for anything.
Re:Escaping from Anaconda's Stranglehold on macOS
by analog31 on Monday September 02, 2024 @04:04PM
(#41428368)
This is a good point and something I hadn't thought about. I'm also a happy Windows user, and have never had a problem with Python installations. But like you say, Python isn't baked into the system.
I do use one piece of commercial software that includes Python. You can see the installer saying "installing Python." I suppose it should fall on the OS and software vendors to not abuse the infrastructure... "to whom much is given, much is expected," but maybe too much to expect.
Re:Escaping from Anaconda's Stranglehold on macOS
by rbanffy on Monday September 02, 2024 @04:28PM
(#41428536)
I remember that, in the past at least, one could completely destroy a Red Hat install by messing too much with the system Python.
Re:Escaping from Anaconda's Stranglehold on macOS
by analog31 on Monday September 02, 2024 @04:36PM
(#41428600)
I guess "Python is my operating system" has its unintended consequences. ;-)
Re:Escaping from Anaconda's Stranglehold on macOS
by swiftcoder on Monday September 02, 2024 @04:14AM
(#41423549)
To be clear, there's absolutely nothing broken about the system Python in the article. There is just a shell alias causing the anaconda version of Python to be launched instead when you type `python3` at the command prompt...
While not familiar with macOS (topic of this article), I think the Mac installer works the same.
On Debian of course you can cause great damage because the system Python is used for critical system functions. This is silly, I think the system python should be an isolated install in /usr/sbin. Better yet, move back to Perl for the system.