Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle the "untrusted" workspace #510

Closed
dhruvmanila opened this issue Jul 3, 2024 · 0 comments · Fixed by #523
Closed

Handle the "untrusted" workspace #510

dhruvmanila opened this issue Jul 3, 2024 · 0 comments · Fixed by #523
Assignees
@dhruvmanila

Comments

@dhruvmanila
Copy link
Member

I think it would be good to handle the "untrusted" workspace case before the release but we can do it as a follow up pr.

A future improvement could be to handle the case where no python installation was detected.

We should make sure to test this change on Windows. Do you have access to a windows machine?

Originally posted by @MichaReiser in #443 (review)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dhruvmanila dhruvmanila

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for untrusted workspace astral-sh/ruff-vscode
1 participant
@dhruvmanila