Improve behavior of reticulate Quarto documents (R & Python together)

[coatless]

Positron Version:

Positron Version: 2024.06.1 (Universal) build 54
Code - OSS Version: 1.90.0
Commit: 5115c73
Date: 2024-07-03T03:51:33.756Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0

Steps to reproduce the issue:

1. Create a new Quarto Document in a Positron session with both a Python environment & R environment activate
2. Inside the Quarto document, place:

---
format: html
---

```{r}
plot(1:4, ylab = "some numbers")
```
```{python}
import matplotlib.pyplot as plt

plt.plot([1, 2, 3, 4])
plt.ylabel('some numbers')
plt.show()
```

3. Run each chunk individually.
4. The Python chunk creates a pop-up window under Ark.

What did you expect to happen?

I expected:

1. the plot window to catch
2. reticulate plugin to default to the active python environment without needing to setup a default python environment

Unexpected plot pop-up:

Expected plot history:

Were there any error messages in the output or Developer Tools console?

N/A

[juliasilge]

Wow, interesting 👀

Can you say more about how you triggered that call to reticulate::repl_python()? I can't figure out how to get that to happen.

If I have a polyglot .qmd and I use, say, Cmd+Shift+Enter to send lines of code to the console for execution, I see the code execute in the correct console (R in the R console, Python in the Python console) and both plots in the Plots pane:

[coatless]

A few videos:

When saved in a project:

quarto-graph-bug-and-repl.mp4

Empty/untitled document (this sometimes won't render when saying reticulate environment has "no")

dry-start-positron-quarto-graph-bug.mp4

I suppose another question is: what environment is reticulate using if its not detecting the default being available?

[juliasilge]

Ah, you were clicking the "Run Cell" button! I believe this will take a PR to the Quarto extension sort of along these lines to fix:
quarto-dev/quarto#436
We'll need to navigate whether to go through reticulate at all for interactive code execution. (Rendering the document will of course have to go through reticulate.) Related to the second bullet in #1646 (comment).

As a short term workaround, you can use use Cmd+Shift+Enter to send lines of code to the console for execution, although for Python then you are running into the first bullet at #1646 (comment).

Please do add anything to that other issue that you think is relevant. We'll keep this one open as a specific case to check when we make changes to the Quarto extension.

[coatless]

@juliasilge role-playing the student and newly minted DS analyst with a button > keyboard shortcut mindset.