For those in the #rstats world, have you migrated from #rstudio to #positron? I am finally trying Positron; love the auto dark mode, which I previously had to use a script to do in rstudio. and it seems to be executing code fine using the here() package to point to files in a directory. What are your thoughts? Excited to see about Python where I was using a mix of the Rstudio/reticulate and Spyder that never worked the way I wanted.

I now have opened a python project, set it successfully (and quickly!) to a particular environment and remade some analyses!

My next test will be to do some Python spatial stuff and see if it shrieks something about wheels at me and explodes

For over a month I have been using #positron. In most cases it is pretty much living the dream of working with R and Python from the same directory simultaneously! I like how it handles Git. I also now have the full universe of VS Code extensions available! There are some little things that Rstudio still handles better. For example, some piped tidyverse code does not carry indents to the next line correctly for some reason. It can be used to develop shiny apps honestly easier than Rstudio, but it doesn't have the convenient shinyapps.io publishing GUI (I think?). I haven't done rMarkdown work with it yet, so I can't say whether they've achieved feature parity there. But it sure is convenient being able to work in both languages from one IDE!
@dantheclamman This was one of the things I loved about working in a notebook-style environment like Zeppelin or Databricks. The ability to seamlessly swap between languages while passing context & data structures between them.