News for hackers. Stuff that matters.
Re:Escaping from Anaconda's Stranglehold on macOS by orlp on Sunday September 01, 2024 @07:07PM (#41421137)
What I do on every dev machine is build Python from source and install it to ~/.localpython and put it in my path.

Then I can pip install away care-free, and quickly run scripts / repls without having to activate an environment.

Re:Escaping from Anaconda's Stranglehold on macOS by eru on Sunday September 01, 2024 @09:12PM (#41421715)
Why does it need to be built from source for that?
Re:Escaping from Anaconda's Stranglehold on macOS by orlp on Monday September 02, 2024 @02:20AM (#41423054)
It doesn't, but it's typically the simplest (for me). It also means I get exactly the version I want compiled with the best optimizations for that machine.
Re:Escaping from Anaconda's Stranglehold on macOS by eru on Monday September 02, 2024 @03:52AM (#41423462)
Thanks, that makes sense.
Re:Escaping from Anaconda's Stranglehold on macOS by m0llusk on Tuesday September 03, 2024 @03:21PM (#41438216)
Typically building from source is done to include optional components such as with the ./configure --with-pydebug option. With many projects make doc is an option because so many prefer to skip that part of the build in favor of online documentation.
Re:Escaping from Anaconda's Stranglehold on macOS by sevensor on Sunday September 01, 2024 @11:12PM (#41422310)
Building Python is so quick and easy I’ve built an interpreter per project in some circumstances. Sometimes more if I want to make sure it’s compatible with multiple Python versions.