-
Notifications
You must be signed in to change notification settings - Fork 82
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
Automatic discovery of Pixi R interpreters #3724
Comments
That is great to see, never came across pixi but seems like a great way to manage environments. I'd also like to flag micromamba, the most efficient way to set-up and configure Python envs I've come across. No built-in support in VS Code but there's a good extension: https://marketplace.visualstudio.com/items?itemName=corker.vscode-micromamba Would Pixi supercede the need for micromamba support @roaldarbol? You've saved me opening a feature request if so! |
Also see prefix-dev/pixi#1543 by the author of the original post. |
@Robinlovelace It will! So the guys at prefix are the same folks behind mamba, and pixi is their "new" flagship - mamba will of course still be supported as I understand it. I use pixi now with all my projects, and we're just laying final touches on the last missing features to make it the option for R too - I currently have some nice mixed R/Python projects managed in the same environment, fully reproducible and IDE-independent. 😊 |
Very cool, keep up the great work! |
Thank you for the info! Since we're currently using a fork of the vscode-python extension, the new pixi locator should just work once we've merged the latest release from upstream 🤞 |
@seeM That sounds great! How about discovery of R installation? Since it's also possible to download R from conda-forge, that can also live in |
And just to think ahead, once if Julia gets better support (#3679) - and since Julia is also on conda-forge - could that become discoverable too. :-) |
This may not be the best place for this question but the above comms makes me wonder: is there a way to default to a system installation? That could reduce bandwidth and HD resources of installing software multiple times on different environments. Or would you just not use pixi when you want to use system installation? |
There is, you can |
It would not affect R discovery, since that is a totally separate extension with its own machinery at this point. |
Which extension is that? And I guess that is then the crux of this issue. :-) |
Let's use this feature to track interest in supporting Pixi interpreters for R. Thanks! 🙌 |
The discovery of Python pixi interpreters has just been released in the vscode-python extension. |
This is great to see! Any chance of Positron using that extension or will it be a case of developing parallel functionality 'in-house', I wonder. |
They already do - so as soon as the new release gets merged here, it should work.
|
@roaldarbol is correct! The latest vscode-python release is a bit more complicated than usual (they've reimplemented environment discovery in Rust, which means we have to get the Rust toolchain + build setup properly too – also means much faster discovery! 🎉), so this update will take us a little longer than usual to merge. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Just FYI for Pythonistas: Since this issue no longer tracks the Python installation, I think it went under the radar - but Positron does now discover Pixi Python installations. 🚀 |
On top of python interpreters from conda/mamba and global R installations (e.g. with rig), they can both be installed with pixi to pin versions within a single project - incredibly useful when it comes to reproducibility.
So this feature request is for the automatic discovery of interpreters living inside a
.pixi
folder inside the opened project/folder. Note, that this has just been implemented for VS Code (for Python only), but does not work in Positron. Maybe it can be patched, or there's possibly help to find in that PR. In any case it would also need to be implemented for R interpreter.The text was updated successfully, but these errors were encountered: