Pixi editable pypi packages aren't visible to VSCode Pylance

[kcajf]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

install a pixi editable module, set the python interpreter in VSCode to the pixi interpreter, and try to import the editable module. VSCode won't be able to find it (i.e. go-to-definition won't work).

Issue description

microsoft/pylance-release#3473

I think this issue explains the problem. It doesn't look like pixi installs editable dependencies in a way that pylance (and it seems like a few other tools) understands.

Expected behavior

Pip has a config setting for this. Not sure if something similar would be suitable for pixi?

[olivier-lacroix]

@tdejager this may be a good reason to switch the default build backend to hatchling? what do you think?

[olivier-lacroix]

Looks like hatch is not enough. See microsoft/pylance-release#6218

[Hofer-Julian]

Looks like hatch is not enough. See microsoft/pylance-release#6218

This pylance issue is closed now, does this mean we can close this one as well?

[olivier-lacroix]

It seems to be a bit hit and miss. It works for some people in our team, and for some days… making it hard to understand what is happening.

[ruben-arts]

Closing for now, reopen if we've got a more concrete reproducible situation.

[kcajf]

This is still a problem for me.

[oliver-batchelor]

I'm just getting into pixi now and having the same problem, I used to have to install my ediable packages with "editable_mode=compat" to make this work.

I have the pixi environment selected, all seems well but the local packages aren't recognised like before?