This whole process demotivated so much that I reverted back to programming in R and RStudio the week after. This was already taking much, much longer than the few hours I had planned for setup. And I personally really dislike making regrettable decisions or committing to something suboptimal.
Maybe I start simple, in a (code) editor? However, here we have Atom, Sublime Text, Vim, and Eclipse? All these decisions.
However, what’s this Spyder alternative other people keep talking about? Come again, there are also Rodeo, Thonny, PyDev, and Wing? What about those then? A whole other group of Pythonista’s said that, as I work in Data Science, I should get Anaconda and work solely in Jupyter Notebooks! Okay…? But I want to learn Python to broaden my skills and do more regular software development as well. P圜harm seemed to be quite fancy for Data Science. As an rational consumer, I went online to read about what people recommend as a good IDE. With Python installed, the obvious next step was to find the RStudio among the Python IDE’s and get working in that new environment. Nothing I couldn’t handle in the end, but my good spirits had dropped slightly. I was getting all kinds of error, warning, and conflict messages already, only 10 minutes in. I had one for the R reticulate package one had come with Anaconda another one from messing around with Tensorflow and some more even.
And apparently, they were in grave conflict. Oh boy, what was I wrong.Īpparently, there were already a couple of versions of Python present on my computer. Coming from R, I had expected to be coding in a handy IDE within an hour or so.
Obviously, the first step was to download and install Python as well as something to write actual Python code. One afternoon three months ago, I sat down, motivated to get started. I must say that getting started was not easy. After several years of proscrastinating, the inevitable finally happened: Three months ago, I committed to learning Python!
0 kommentar(er)
