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.

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

Fallback to using bundled executable if Python interpreter is unavailable #598

Open
dhruvmanila opened this issue Sep 3, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@dhruvmanila
Copy link
Member

Based on the discussion thread from #493 (comment).

Once we switch completely to the native server, it might make sense to use the bundled executable as a fallback and remove the hard requirement of the Python interpreter.

@zhuoqun-chen
Copy link

zhuoqun-chen commented Feb 18, 2025

Hi @dhruvmanila, do you have ideas about if there's any progress on this thread? I prefer having a global bundled ruff executable through the extension itself in my workflow to lint my scripts. And how do I know bundled ruff executable path so that I can use it by default?

@dhruvmanila
Copy link
Member Author

@zhuoqun-chen You can use ruff.importStrategy with "useBundled" to explicitly use the bundled executable by default.

@zhuoqun-chen
Copy link

@zhuoqun-chen You can use ruff.importStrategy with "useBundled" to explicitly use the bundled executable by default.

Thank you very much, yeah this is the option I'm looking for!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants