Issues working interactively in a combined {python} and {r} Quarto document

[Art-Ink]

Hi,

I have come across two issues when working in a combined {python} and {r} Quarto document. I have a uv environment in my project folder, and reticulate is set correctly. Rendering the document also is no issue.

First: Python chunks executed interactively

However, I noticed, that when I work through the document chunk by chunk to debug or just interactively explore some new data, that clicking the "run" button over python chunks executes the chunk but does not store the created output in the running uv environment. Instead the objects disappear, it seems that a new python environment is started when I click the button, since I see a call to repl_python() in my console. See below for an example.

reticulate::repl_python(quiet = TRUE, input = r"--(

+ some_object = {
+   8:14
+ }
+ 
+ 
+ )--")

When I instead go into the chunk and execute line by line with cmd+enter the variables are added to my uv environment.

The expected behavior would be that analogous to how r chunks are handled I can see the variables I create in python in my variables pane.

Second: Run all not working for consecutive {python} chunks

When I work on the document I usually start the day by clicking run all on the last chunk and continue my work. However, I noticed, that this does not work when the chunk directly above the last chunk is a {python} chunk. In this case only the repl_python call I described in the first issue goes to the console. When I add an empty {r} chunk above it restores the correct behavior of running all chunks above the current one.

Thank you and I hope these issues have not been described somewhere before and evaded my searching.

Best

Christian

[juliasilge]

Thank you for this report! 🙌

I believe we are tracking problems like this in #6675. Want to take a look to see if you agree, and add a 👍 plus any additional info on your use case? If you can specifically mention your second symptom, that would be helpful so we can understand how this is playing out in reticulate Quarto documents.

[Art-Ink]

Thank you Julia for linking this. It is indeed similar to the issue I have but #6675 does not cover that anything that gets sent to the reticulate console is not available via the py$ syntax.

py$some_object is not available when I try to access it through R. But reticulate is running since py$r is available.

I will add this to #6676 as well.