How to import run_quarto into active Python session?

[enryH]

Description

I would like to use quarto-cli programatically, however I am not able to import the run command.

import quarto_cli # works
from quarto_cli import run_quarto # does not exist

I am looking at the Python package which is used to set the entry point in setup.py. see quarto-cli/blob/v1.6.42/quarto_cli/init.py

[mcanouil]

You are looking at Quarto CLI codebase. It's not a Python module, so you can't import the content.

Look at the Python module/wrapper around Quarto CLI: Quarto Python module GitHub repository.

Side note: avoid using "here" as link text which convey no meaning of what the link is about. See Writing meaningful link text (WCAG).

[enryH]

true about the link. Normally I know this:) I updated it. Thanks for the hint. I will have a look!

[enryH]

So my aim is to run quarto from within a bundled (PyInstaller) distribution. I can manage to execute the package binary, but when it comes to execution of qmd or ipynb notebooks I fail to patch the execution paths correctly.

If I see this correctly programs that rely on subprocess.run (or related) calls do not work including the quarto package: quarto/render.py#L76 (as PyInstaller does not have natively a Python executable shipped)...

[cderv]

If you have a reproducible example to share, you can maybe open an issue in https://github.com/quarto-dev/quarto-python so that it is tracked in the right place.

PR are welcome there too if you have ideas from improvment.

[enryH]

It will be a bit involved to create a simple example, but I can make a branch from our project where I document that.

Testing it today, I see that quarto implements it's own set of function to execute notebooks (qmd or ipynb). I could manage to find a workaround where I use nbconvert programmatically to execute the notebook and use quarto binaries to render the execute ipynb as these are not natively executed. nbconvert execute API. But this only works if one adds a Python executable to the bundle manually.

Before I build it on a separate branch, see Multiomics-Analytics-Group/vuegen@a13e784