Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Escaping from Anaconda's Stranglehold on macOS

paulromer.net

Post reply on HN
Print view View original

81–90 of 286 posts

Re: Escaping from Anaconda's Stranglehold on macOS

#81

Post by puppycodes »

I always appreciate a post about a simple fix to a problem a lot of folks run into thats not esoteric and lays it out simply :)

As engineer of many many years now all I can say with certainty is that confusion, failure, research and eventually small successes have been the central theme of working with computers. I personally love the struggle and mystery but its not for everyone. At the end of the day its about what you want to get out of it. If you want to write programs without learning about the terminal go for it, but I would say there are better gilded cages with GUIs that help you get a lot more done within that constraint.

If you want a deeper understanding, I think its more helpful to admit you can't cheat the process of learning. Slow is the only speed.

Re: Escaping from Anaconda's Stranglehold on macOS

#82

Post by cowsandmilk »

mattl wrote: post #3

This seems like a lot of work to bypass something in the zshrc file vs. doing something in a terminal emulator? I would assume Python developers are somewhat forced to use a command line anyway.

As described on https://docs.python.org/3/using/mac.html , python on MacOS both ships with an IDE and the ability to run scripts without using the command line.

Re: Escaping from Anaconda's Stranglehold on macOS

#85

Post by cowsandmilk »

tkuraku wrote: post #76
brewmarche wrote: post #15

You can just keep Anaconda and just use it as a pyenv replacement, e.g.: conda create -n "myenv" python=3.8 conda activate myenv Then just use pip in your environment, if you don’t like conda packages. Not sure what the paragraph about being able to install multiple Python versions after getting rid of Anaconda is about.

This would be the sane advice.

No, because half the students in your 200 person class don’t have anaconda installed and now you are managing students in yet another state of python environment management with TAs who are economics grad students, not python experts

Re: Escaping from Anaconda's Stranglehold on macOS

#87

Post by adolph »

dumbo-octopus wrote: post #74
apetresc wrote: post #69

> 10. What Changes When You Are Free > You will not be forced to work inside something known as a “virtual environment.” Oof, this terrible advice cancels out an otherwise reasonable post. Beginners who don't know what they're doing are the last people who should be `pip install -r requirements.txt`-ing into the system Python the way this article is recommending. That's not only going to make working on multiple proj…

Yes. I recently had to debug my gf’s entire work computer setup getting fubar’d from installing a pip package at a user level that conflicted with the name of some package used internally by the 10k+/seat/year software the company devices have installed. Proximal cause? The installer “helpfully” failed over to installing at the user level when she didn’t have permissions to write to the place she told it to. Root cau…

> package used internally by the 10k+/seat/year software the company devices have installed

Sounds like a skill issue that shouldn’t be seen in “10k+/seat/year software.” I wonder what other fails are in it.

Re: Escaping from Anaconda's Stranglehold on macOS

#88

Post by adolph »

zjp wrote: post #83

I still don't really get what conda is or does. AFAIK it ensures ABI compatibility between Python packages that have C extensions? Does manylinux and the limited API not take care of this?

Way back Anaconda was an accessible way to get Numpy running without having to scrounge up a Fortran compiler for one’s MacOS version.

Re: Escaping from Anaconda's Stranglehold on macOS

#89

Post by simonw »

atoav wrote: post #57
latchkey wrote: post #43

Earlier quoted context omitted.

"If you teach a course that requires Python" "Many of these students have not used the command line." I'd suggest that we are failing to teach students learning to code, the basics of how to use computers. Pre-requisite should be a class on how to use the command line.

I thought a class of entirely non-tech art students how to use the commandline to run their python code within an hour and that includes distractions like people using multiple different operating systems and explai ing how paths work on each. Tech inclined students get the gist of the whole thing in less than 15 minutes. The CLI is literally just: You write a command and a thing happens. That isn't a thing that peop…

A lot of students arrive at university these days without understanding what files and folders are: https://www.theverge.com/22684730/students-file-folder-direc...

Re: Escaping from Anaconda's Stranglehold on macOS

#90

Post by adolph »

chunkyks wrote: post #48
adolph wrote: post #4

Anaconda’s hidden license for institutions is a dark pattern time bomb for scientific computing.

We've been hit by this. When I talked to them four years ago, they agreed we were good to use it for free, no problem. The dollar figure they're asking for would make it the single most expensive software product we would be licensing in our enterprise, by a lot. The deadline is absurdly soon for such a big deal. And they opened discussion in an incredibly hostile manner and have made no attempt to work with us. So,…

> And they opened discussion in an incredibly hostile manner and have made no attempt to work with us.

With $$ for unlicensed period too?

Post reply on HN