Bundled Quarto not found if not on PATH and using Pyenv #4511
Comments
juliasilge
changed the title
|
From @jmcphers:
|
|
@testlabauto created a work around for this issue. Once we make this fixed we will need to change our Quarto tests to ensure they are working as expected. |
13 tasks
isabelizimm
added a commit
that referenced
this issue
Nov 14, 2024
Related to #4511 the Python extension is using a newer version of VSCode, with a `GlobalEnvironmentVariableCollection` which overwrites other extension's contributions to environment variables, such as PATH. This moves to using `EnvironmentVariableCollection`, which will only touch its extension contributions. From what I understand, the original change was made to be able to set multiple folder level scopes in a workspace, eg, set different interpreters for different folders inside a workspace: microsoft/vscode-python#20492 (comment) and microsoft/vscode#171173 Positron operates (or at least the interpreter dropdown UI shows) 1 interpreter per workspace, so I don’t think the scoping stuff applies to us. ### QA Notes - make sure Quarto is in your local `positron` directory. AFAICT this does not automatically populate on `yarn` runs, so you might have to put it there manually. (At build time, it is at `~/Applications/Positron.app/Contents/Resources/app/quarto/bin`, which is being properly identified by the Quarto extension 👍) - delete other local Quarto installations (likely by running `rm -fr ~/Applications/quarto`) - open up Positron - run `quarto --version` in terminal, should not give any errors --------- Signed-off-by: Isabel Zimmerman <[email protected]>
Verified FixedTest scenario(s)Verified by removing local quarto cli install. Note that the "workaround" mentioned in the comments needs to stay where it is because dev build do not have the bundled CLI. Link(s) to TestRail test cases run or created: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Need to handle quarto-dev/quarto#517 on the Positron side.
System details:
Positron and OS details:
2024.08.0-77
OSX
Interpreter details:
Any
Describe the issue:
See quarto-dev/quarto#517
Steps to reproduce the issue:
See quarto-dev/quarto#517
Expected or desired behavior:
Bundled Quarto can be used without a seperate Quarto install
Were there any error messages in the UI, Output panel, or Developer Tools console?
See quarto-dev/quarto#517
Once we have fixed
We will need to make changes to our Quarto tests. @testlabauto created a work around for this issue. Once we make this fixed we will need to change our Quarto tests to ensure they are working as expected.
The text was updated successfully, but these errors were encountered: