Create outline of Python environment management eco system

[SamEdwardes]

Reference

• https://pycon.switowski.com/02-packages/

Content ideas

I propose that the following items should be included:

• Overview of the ecosystem
  • 
• Deep dive into poetry (Deep dive into poetry #32):
  • usage
  • how it works behind the scenes, and what that means to you (high level)
  • collaborating with poetry
  • publishing content to RStudio Connect
  • Choosing package source (pypi, artifactory, rspm)
• Deep dive into venv:
  • usage
  • how it works behind the scenes, and what that means to you (high level)
  • collaborating with venv
  • publishing content to RStudio Connect
  • Choosing package source (pypi, artifactory, rspm)
• Deep dive into conda:
  • usage
  • how it works behind the scenes, and what that means to you (high level)
  • collaborating with conda
  • publishing content to RStudio Connect that was developed with conda
  • Choosing package source (forge vs. anaconda)
• comparison of renv:: vs. venv vs. poetry vs. conda workflows (e.g. similar to this https://pandas.pydata.org/pandas-docs/stable/getting_started/comparison/comparison_with_r.html)

The following items should be excluded:

• deep dive into pipenv: both third party library that is similar to poetry. It is valid to use over poetry - but would be duplicative of us to go over both.

[dpastoor]

note of existing article around python stuff: https://solutions.rstudio.com/python/minimum-viable-python/

[dpastoor]

@SamEdwardes you mentioned we prob shouldn't bring up virtualenv as its deprecated?? compared to venv and friends, or did I hear you wrong?

If so we should make a note for support - which suggests virtualenv: https://support.rstudio.com/hc/en-us/articles/360023654474-Installing-and-Configuring-Python-with-RStudio which was linked from: https://solutions.rstudio.com/python/configure/#want-to-help-users-get-started-with-python-and-rstudio as we trace some breadcrumbs

[SamEdwardes]

Agreed we should try to drop references to virtualenv. As of python 3.3 the venv module is part of the standard library, so there is no reason or benefit for users to pip install virtualenv.

Users should ideally be using at least python 3.7. As of December 2021 python 3.6 is end of life.

[SamEdwardes]

Closing this issue - it is now covered by https://github.com/rstudio/solutions.rstudio.com/pull/246.