Issues with pip install quarto-cli

[leemhmark]

Description

I keep encountering the following build errors when trying to pip install quarto-cli on my Windows machine and I'm not sure how to resolve it, any suggestions would be great.

[mcanouil]

Unfortunately, a screenshot of an error is not enough.
Please fully describe your setup and the steps that lead to this error.

[mcanouil]

You are mixing issues here. Your last screenshot is unrelated to the issue in this thread. If you can't install Quarto, of course the Quarto VSCode extension won't find it.

Your environment is the issue, but without the means to "copy" it, it's goign to be hard to figure out the issue.

What's your Z volume? If it's a network/cloud drive, please test everything on your local drives. This adds complexities.

Also, why are you setting the DENO_ environment variables? Did you set other things like that?

[leemhmark]

I wasn't setting the DENO_ environment variables, it does that automatically when I activate the environment. As mentioned earlier I was able to conda install quarto in this environment, the problem right now is VS Code can't find that installation.

The terminal was on Z drive since my repo was there, but all my environments were created under C:\users, you can see the same problem when I tried to do it in C:\

[cderv]

Also, why are you setting the DENO_ environment variables? Did you set other things like that?

@mcanouil this happens when running quarto.cmd. No need to assume user's is doing it - it is us. quarto.cmd is a script that will run on windows using BAT.

It will be especially used by conda-forge of Quarto which don't build an .exe.

Now why this script is ran ? It seems the conda environment does run quarto but it is possible there is an issue while running Quarto and so why the VSCODE extension is saying "not found" because quarto install is not running.

@leemhmark you should take a step back and check that outside of VSCODE you get a running quarto installation.

• If you are using conda, create a new clean environment in terminal, install quarto from conda-forge and check that it is working.

• If you are not using conda, use python directly with a venv (see example below Issues with pip install quarto-cli #11380 (comment)) and install with pip install. though you need to be sure when doing that you are not using any conda environment, conda binary or else.

Mixing conda and other install is not easy to handle on windows, I had really bad experience with that.

So I would try to have things working the way you want in Terminal only. Then when it is working try again VSCODE.

Also, just a reminder that there is no need to install quarto using pip or conda. You can install by downloading the right installer from the website, and install on your machine for your user. Installing using pip is advanced usage when pinning a version for a specific project is desired for example.

Hope it helps.

[mcanouil]

Conda is setting these, hum, I really don't understand the appeal of this tool.
It's actually Quarto apparently.

Anyhow, you basically put aside the method to install Quarto via PIP, right?
You've managed to install Quarto via Conda-Forge as you said.
Do you know where Quarto CLI is in this setup (the path)? (probably something like conda/envs/quarto-py313/bin/quarto)

Using the same Docker image as before leads to everything working as intended in the terminal because that's where the environment is activated.

conda create -n quarto-py313
conda init zsh
conda activate quarto-py313
conda install conda-forge::quarto

Does quarto --version work in your activated environment?

If you open a new terminal you'll see that the environment is no longer activated.

Now you need to figure out how to tell VSCode to use this environment everywhere.
VSCode does this natively for local environment when it detects them (.conda inside the workspace), but cannot do that when it's elsewhere, but still the tools won't be accessible to VSCode because it was started before the environment was activated.
In the end, this is still not a Quarto CLI issue.

See https://quarto.org/docs/projects/virtual-environments.html#vs-code.
This behaviour about Conda and VSCode (and extension setting not working) is documented.

[leemhmark]

Ok I'm able to make it work now, basically need to activate the conda environment with the quarto installed and then launch VS Code from there:

1. Open anaconda prompt
2. conda activate quarto-cli_py310
3. code .

Now VS Code launches and the shortcuts do work as it recognizes the Quarto install:

This seems to be the only way so far, consider my issue resolved.

[mcanouil]

Yes, I think there is an issue open in the Quarto VSCode extension repository about opening VSCode from the command line where the environment has been activated.

Glad you found a way to make it work!

[cderv]

Right now I can't reproduce

What I did on my windows environment using uv (https://docs.astral.sh/uv) for managing venv

cd $env:TEMP
mkdir test-quarto
cd test-quarto
uv venv
uv pip install quarto-cli

It installed latest quarto correctly.

Verbose mode, also showed by not issue at the line where you got the error

DEBUG adding 'quarto_cli/share/deno_std/cache/deps/https/cdn.skypack.dev/010ab5a2e2b8bd9419eceeb3654e9d2f1412afd9065e89a8d3d03c58f29970dd'
DEBUG adding 'quarto_cli/share/deno_std/cache/deps/https/cdn.skypack.dev/010ab5a2e2b8bd9419eceeb3654e9d2f1412afd9065e89a8d3d03c58f29970dd.metadata.json'
DEBUG adding 'quarto_cli/share/deno_std/cache/deps/https/cdn.skypack.dev/075584d2a217fa87db56cb38b63393804f62af3308285711316daab6892cebb6'
DEBUG adding 'quarto_cli/share/deno_std/cache/deps/https/cdn.skypack.dev/075584d2a217fa87db56cb38b63393804f62af3308285711316daab6892cebb6.metadata.json'

So probably something related to your environment somehow.