Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixing R and Python code cells in a Quarto document #4321

Closed
Matteo-Valerio opened this issue Aug 12, 2024 · 1 comment
Closed

Mixing R and Python code cells in a Quarto document #4321

Matteo-Valerio opened this issue Aug 12, 2024 · 1 comment

Comments

@Matteo-Valerio
Copy link

System details:

Win 11

Positron and OS details:

Positron Version: 2024.08.0 (system setup) build 31
Code - OSS Version: 1.91.0
Commit: 7ee0596
Date: 2024-08-10T13:58:22.910Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621

Interpreter details:

R 4.4.0 and Python 3.10.9

Describe the issue:

In a Quarto document, when mixing R and Python code cells, the results are not reported in the relative consoles.

image

For R cells the results is reported in the relative console as expected.

image

For Python cells the result is reported in two different ways:

  1. Clicking on the “Run Cell” the code is executed via “reticulate”, the statements are reported in the R console, but not executed, indeed the results are reported neither in the R console not in the Python console and the variables are not set.

image

  1. Selecting the lines of code and executing manually (Ctrl + Enter) the statements are reported in the Python console and are executed correctly.

image

Expected or desired behavior:

Get the same result by running the Python code with the previous two ways.

Were there any error messages in the UI, Output panel, or Developer Tools console?

No

@seeM
Copy link
Contributor

seeM commented Aug 12, 2024

Thanks for the writeup @Matteo-Valerio! We are aware of the issues with mixed R/Python Quarto documents and are already tracking that work e.g. see #1646 (comment).

@seeM seeM closed this as completed Aug 12, 2024
@seeM seeM closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants