Re:Escaping from Anaconda's Stranglehold on macOS
by mr_toad on Sunday September 01, 2024 @11:42PM
(#41422402)
Wouldn’t this end up like the XKCD standards cartoon. You’d have yet another Python package system and even more fragmentation.
Re:Escaping from Anaconda's Stranglehold on macOS
by ethbr1 on Monday September 02, 2024 @12:14AM
(#41422525)
If Python users weren't comfortable living in that reality already, they wouldn't still be Python users.
Re:Escaping from Anaconda's Stranglehold on macOS
by Eisenstein on Sunday September 01, 2024 @11:28PM
(#41422361)
It took 10 years to force a breaking migration from Python 2 to Python 3 in order to handle Unicode...
I have resigned myself to repeatedly smashing my keyboard on the desk until it rains keys in blind rage induced frustration to let off steam and then calmly creating an issue in the appropriate repo instead of allowing even a modicum of hope that this will ever be fixed systemically.
Re:Escaping from Anaconda's Stranglehold on macOS
by superlopuh on Monday September 02, 2024 @03:14AM
(#41423278)
As far as I'm concerned, this is the fix: https://github.com/astral-sh/uv
The Python community needs to solve this ASAP. This almost weekly pain point has turned a language I used to love in college into one of my most despised languages. The fact that the ML community uses this broken platform is infuriating.
Make a Python version 4 that focuses only on fixing the packaging. 100% per-project hermeticy. No global packages whatsoever. Solve just this issue and bring the entire ecosystem on board. Kill all the various virtualenvs, the anacondas, global packages. All of it.
Learn from Rust/Cargo. That project does it mostly right (sans lack of namespaces and reproducible builds).