Current best practice for Python and possible documentation discrepancy

Hi,
Firstly, I'd like to thank the RStudio documentation team for their work. I find RStudio's documentation to be incredibly useful and well-written.

I have noticed two conflicting approaches for installing Python:

I recall that when RStudio's best practice for installing R changed from "install from source" to "install from pre-built binaries", there was a case where not all documentation was updated accordingly (Package Manager documentation if I recall correctly).

In the case of Python, I noticed that the Connect documentation refers to installing from source while the other documentation suggests a Miniconda install via a BASH script.
Just wanted to check if the Connect documentation is up to date or if the Miniconda approach is advised now for Connect also?

Appreciate the feedback.

I have noticed that https://docs.rstudio.com/rsc/integration/python/ is in line with https://docs.rstudio.com/resources/install-python/ so I presume that it's likely an oversight.

It appears that there is some overlap between the Connect install guide (https://docs.rstudio.com/rsc/installation/) and admin guide (https://docs.rstudio.com/connect/admin/).
I guess the documentation release cadence may differ for the two?

In any case, thanks again to the documentation team, I appreciate and value RStudio's documentation.

It appears that the admin guide has now been updated.
Thank you!

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.