quarto-dev / quarto-dev/quarto-cli

Add Quarto environment variable specification/documentation

Open
#8,793 9 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

What would you like to do?

Give feedback or suggest an improvement

Description

Currently, Quarto has several environment variable such as QUARTO_R and QUARTO_PYTHON, but there is absolutely nothing about those.
The variables are mentioned but never defined:

Determine which versions of Python and R are used (e.g. QUARTO_PYTHON, QUARTO_R, PY_PYTHON, or RETICULATE_PYTHON).

In the end users need to figure out what those are and what values are allowed on their own.

Another related issue is that a user can set QUARTO_PYTHON=/very/bad/path and still get Quarto to work without any warnings.

> QUARTO_PYTHON="/bad/path" && quarto render index.qmd 

Executing 'index.quarto_ipynb'
  Cell 1/1: ''...Done

pandoc 
  to: html
  output-file: index.html
  standalone: true
  section-divs: true
  html-math-method: mathjax
  wrap: none
  default-image-extension: png
  
metadata
  document-css: false
  link-citations: true
  date-format: long
  lang: en
  title: Quarto Playground
  
Output created: index.html

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Python, R, and project-environment documentation pages linked in the issue, then reproduce the shown render command with an invalid QUARTO_PYTHON value. Done means the supported environment variables and accepted values are documented and the issue’s requested handling of an invalid path is clarified or addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, r
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.