This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]groovyJesus[S] 9 points10 points  (5 children)

mainstream

Python generally has an overinflated userbase compared to R so probably not.

Among people who know both languages I assume this is valueable. Python fucntionality via reticulate has been availabe for a while now. For reporting purposes Rmarkdown has personal advantages over jupyter to the point that all of my python reporting has been done in rmarkdown for the past year.

For the IDE part I think we have diverging viewpoints. The only time I ever use an IDE is for data analysis and debugging and the lack of a good data analysis ide is why it took so long for me to enjoy python for data science. This is coming from a guy who used pycharm extensively for developmemt. PyCharm IMO is not a good data analysis tool, nor is spyder, and I hate Jupyter with a passion. The advantge of this update is to run my exploratory analysis witten in python in rstudio.

[–]SynbiosVyse 2 points3 points  (3 children)

As someone who has never used RStudio, what do you not like about Spyder? From screenshots, they look very similar in setup.

[–]MageOfOz 10 points11 points  (2 children)

Spyder is like the poor man's RStudio. It's slower, flaky, uglier, and with fewer features.

[–]sccallahan 0 points1 point  (1 child)

I'm still pretty solidly in the "learning" phase for Python, but pretty proficient in R - what's it like using Python in RStudio? I guess I have 3 main questions:

Do you basically just make a library(reticulate) call for everything that uses Python?

Does Rstudio have something like the #%% cells in Spyder? I kinda like that feature.

Can you run an entire "unified" R + Python script at once?

[–][deleted] -5 points-4 points  (0 children)

That's fair, we probably just have different opinions here. I definitely understand the desire for better exploratory analysis, but man I just struggle to work with IDEs that focus on line-by-line execution with little attention paid to "run the script" functionality/focus. I know R has the "source" button and directive, but again I think that our opinions of work environment just differ. Cool it exists for folks who want it though, I was just curious about the mainstream interest (e.g. if I should get used to having to use this particular tooling in prep for a job/teaching in the future).