How can i run python and R code in the same report?

[stefaniecg]

Description

I was rendering a quarto report with only python code and all was ok.
But now i added R code, then the reticulate python complains it does not have the modules i load.

I found this information, that when i mix R and PYTHON it will use reticulate, which i do not want.

Using python and r together If your quarto document includes both {python} and {r} code blocks, then quarto will automatically use Knitr engine and reticulate R package to execute the python content. [ref.]

How i can tell quarto to not use reticulate?
but use my normal python as it was doing before?

The example coad can be as simple as test.qmd:

--- 
title: titulo
author: me
---
```{r}
print("Hello world from R !")
```
```{python}
import panda as pd
print("Hello world from Python!")
```

Thank you for the help you can provide :)

The error is the following:

Error in `py_call_impl()`:
! ModuleNotFoundError: No module named 'panda'
Run `reticulate::py_last_error()` for details.
Backtrace:
     ▆
  1. └─global .main()
  2.   └─execute(...)
  3.     └─rmarkdown::render(...)
  4.       └─knitr::knit(knit_input, knit_output, envir = envir, quiet = quiet)
  5.         └─knitr:::process_file(text, output)
  6.           ├─xfun:::handle_error(...)
  7.           ├─base::withCallingHandlers(...)
  8.           └─knitr:::process_group(group)
  9.             └─knitr:::call_block(x)
 10.               └─knitr:::block_exec(params)
 11.                 ├─knitr:::in_input_dir(engine(options))
 12.                 │ └─knitr:::in_dir(input_dir(), expr)
 13.                 └─knitr (local) engine(options)
 14.                   └─reticulate::eng_python(options)
 15.                     └─reticulate:::py_compile_eval(snippet, compile_mode)
 16.                       ├─reticulate::py_capture_output(...)
 17.                       │ ├─base::tryCatch(...)
 18.                       │ │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
 19.                       │ └─base::force(expr)
 20.                       └─builtins$eval(compiled, globals, locals)
 21.                         └─reticulate:::py_call_impl(callable, call_args$unnamed, call_args$named)



Quitting from lines 25-27 [unnamed-chunk-2] (test.qmd)
Execution halted

[mcanouil]

You can't as documented: one document = one engine.

engine: knitr means you will execute Python through R thus reticulate.
engine: jupyter means you will execute R or Julia through Python thus rpy2 etc.
engine: julia, well you got the point I believe.

You should really consider going through the documentation at least quickly: engines, kernels, how computations happen, etc. are all described. There are no shortcuts to learn how Quarto works.

https://quarto.org/docs/computations/execution-options.html#engine-binding

Edit: to be clear, it's fine to ask questions but it's far more effective for everyone to go to the documentation for the basics.