-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support Ribasim checkout #85
Conversation
@DanielTollenaar do you have time for a review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@visr, if you can describe how I can use the dev env in vscode (using your bat or otherwise) I think all is OK. Checked the envs and dev is indeed pointing to the ribasim-repos at the same level as ribasim-nl
Users need the latest version of pixi: https://prefix.dev/
@@ -0,0 +1 @@ | |||
pixi run --environment=dev code . | exit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should work better once VSCode recognizes pixi environments. Does this work for you? prefix-dev/pixi#411 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reading that issue, you mean selecting the interpeter from the dev-env by this method: https://code.visualstudio.com/docs/python/environments#_manually-specify-an-interpreter?
Did some more checking; that doesn't work if I try to select the dev-env python.exe, but does work if I try to select the default-env python.exe
But I managed to find a workaround:
- start a normal terminal
Terminal
->New Terminal
(or ctrl+shift+') - this dóes start in the dev-environment if you run vscode in the dev-environment
- if you now open a interactive window, it starts to use the dev-environment as wel. And is also appears in the list of python environments to select from
Strange, but I think this is as good as it gets for now, so let's merge :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is curious, glad you found a workaround though.
Fixes #84.
This adds a Pixi
dev
environment, which points to the Ribasim repository, which is expected to be cloned next to this repository. To launch VSCode in this environment, useopen-vscode-dev.bat
. I addedopen-vscode.bat
as well to open the default environment, which points to the latest ribasim release.https://pixi.sh/latest/reference/configuration/#the-feature-and-environments-tables