61–70 of 286 posts
Earlier quoted context omitted.
Same here. It’s not that bad of a solution when you think about it.
Anaconda (and miniconda) is a very good solution if you need a container-like environment. I can easily go back to old projects with different python versions and do maintenance in them with no hassle.
Earlier quoted context omitted.
This guide requires holding down arcane secret key combination, this is not remotely normal way to do anything, and prevents people from learning basic system commands every programmer needs to know. Also, “mv ~/.zsh ~/zsh-anaconda”.
His audience is not programmers.
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.
Most of the kids the author is talking about aren't going to ever code for a living - they're going to code to get their job done. It's a very different mindset.
Clickbait title (“stranglehold”, really?), and also really bad advice. Terminal can be scary, but “open terminal from Applications/Utilities” and typing “rm ~/.zsh” is objectively easier. Also that’s not even the best solution, just a far better way to do this solution.
Pythons and anacondas are snakes which catch and kill their prey by strangling them and inducing cardiac arrest. It’s a pun.
As expected, I see comments here like "Avoiding sh overcomplicates this." It's true. I found the shell-avoiding instructions no better, and possibly worse, than shell commands. But: what's sauce for the end user goose is sauce for the developer gander. Developers are users. Give developers good visual tools. Sadly I don't think there is a visual front end to git,, for example, that is any good among the handful I hav…
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…
Earlier quoted context omitted.
Most of the kids the author is talking about aren't going to ever code for a living - they're going to code to get their job done. It's a very different mindset.
By that logic... we might as well stop teaching math because kids are never going to become mathematicians.
Earlier quoted context omitted.
Anaconda (and miniconda) is a very good solution if you need a container-like environment. I can easily go back to old projects with different python versions and do maintenance in them with no hassle.
pyproject.toml is a better solution
Conda packages compiled such that the search paths of the binaries are not using the OS's (which why the Linux DE Qt theme doesn't work for Spyder).
Conda also comes with well optimized binaries for high performance compute which is absolutely a must for modern data science.
> 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 projects nearly impossible (especially for the kind of beginning students who get recommended Anaconda, which are almost always the Data Science-y crowd using NumPy, Pandas, Scikit, etc, which are notoriously finicky with version conflicts), but it stands a good chance of breaking other Python-based system utilities in completely opaque ways. This sort of advice can fubar a naive user's entire workflow.
I know virtualenvs suck to explain to people, but in my opinion it needs to be done before you ever tell them about `pip install`.
As expected, I see comments here like "Avoiding sh overcomplicates this." It's true. I found the shell-avoiding instructions no better, and possibly worse, than shell commands. But: what's sauce for the end user goose is sauce for the developer gander. Developers are users. Give developers good visual tools. Sadly I don't think there is a visual front end to git,, for example, that is any good among the handful I hav…
Wish there was something like magit outside of emacs that I could recommend to people.