docs: Provide guidance on using direnv

[phreed]

Specifically, guidance on using direnv in the context of IDE's

[pavelzw]

The Python extension also has proper pixi support, we should mention that IMO

[phreed]

You mean this https://code.visualstudio.com/docs/python/python-quick-start extension, correct?
I do not see an explicit mention of pixi.
I suppose it is something similar to conda?

[pavelzw]

yes it's this extension. maybe add an image guide on how to do it?

[Hofer-Julian]

Yeah, If we have a proper vscode section, the Python extension should be mentioned as well 🙂

[phreed]

I am not entirely sure how to use the python extension with pixi.
I saw that there is some effort to make a pixi conda but I do not think that is the way to go.
I am looking for a way to use conda run ... as that should be translatable to pixi run ....
But, I am not finding that.

[phreed]

I suppose trampolines could be used as the target of

but, trampolines are not provided as part of project workspaces.

[phreed]

I suppose it comes down to the settings.yml for the python plugin:

https://code.visualstudio.com/docs/python/settings-reference

It is not obvious to me how this should be configured.

[Hofer-Julian]

It should no configuration.

I just created a fresh Pixi workspace with Python, started vscode in it and vscode immediately selected the pixi environment. Maybe @baszalmstra can check if something is broken on Windows at the moment?

[Hofer-Julian]

Looks good at first glance, will try to find time to give a proper review later

[Hofer-Julian]

I've cleaned things up a bit, and I think it looks good now.

Thanks for your contribution @phreed!

[phreed]

The combination of the VSCode stuff into a single page makes sense, as VSCode is a single application.
I have found that the isolation provided by pixi is sufficient to make use of devcontainer (on linux at least) unnecessary.

I am not so sure about combining the Jetbrains stuff into a single page though, PyCharm, Idea.
They are separate applications produced by the same vendor.
I should have called the new page for Jetbrains/IDEA, idea.md rather than jetbrains.md.

[Hofer-Julian]

I am not so sure about combining the Jetbrains stuff into a single page though, PyCharm, Idea.
They are separate applications produced by the same vendor.
I should have called the new page for Jetbrains/IDEA, idea.md rather than jetbrains.md.

I see your point, for now I think it's fine. If more content comes up where the JetBrains products differ, we can split them again

[phreed]

I did start a branch to capture the point about jetbrains products.
main...phreed:pixi:jetbrains-docs
That said I guess this MR is done.