Hey all,
I just ran down some more tips and tricks to get Python running. Should we go through all the hassle? Yes, I think we ought to for several reasons. First, Python is a much faster programming language for Bayesian analyses. There are more resources to run these models compared to R (or any other language). Second, while Python may be difficult to integrate (as of today) with RStudio, it is the future for data analysis and it would be a shame to miss the opportunity to learn how to use it. Third, and this might be the kicker....Python is simpler. You can run the same models in Python that you run in R with far fewer lines of code (and it is faster). So, from a data analysis and "data scientist" perspective, it makes all the sense in the world for us to push through the pain and learn how to run Python. With that being said, I realize that the reticulate package is in its infancy. There are some glitches that will be worked out over the next few months. Bear with me. Learn to execute Python from within R and vice versa.
The reticulate online help has actually improved over the past few weeks. Here (below) is one thing to help you get Python located with R. Be sure to go through the steps and don't just copy and paste the code into your interpreter. Read what they say. Most of the problems you are likely facing stem from the location of Python (i.e., the actual binary interpreter command). So peruse this link material:
If you don't find that helpful, start diving into the other articles listed on the website. Many of these articles are focused on certain operating systems. I use Linux. Haven't had a problem on my desktop at all running Python with RStudio but, then again, Linux relies heavily on Python.