prefix-dev / pixi

Package management made easy
https://pixi.sh
BSD 3-Clause "New" or "Revised" License
3.2k stars 175 forks source link

Make pixi env conda compatible by default #1877

Open cdeil opened 2 months ago

cdeil commented 2 months ago

Problem description

@pavelzw - thank you for making https://github.com/pavelzw/pixi-pycharm and documenting how to use it in https://pixi.sh/latest/ide_integration/pycharm/

I'm a new user and it's working for me.

That said, I think it would be even nicer if pixi just had better conda env compatibility by default.

Is it possible / does it make sense to have this "conda shim" whatever it is built in and on by default for any pixi env?

Are there significant downsides / cost in terms of install speed or number of files or some other drawbacks?

nicornk commented 2 months ago

+1

pavelzw commented 2 months ago

IMO the conda shim is a too hacky fix to be in pixi's default workflow. JetBrains should instead either allow better python plugins (xref https://youtrack.jetbrains.com/issue/PY-63692/Python-local-interpreter-panel-dont-show-third-party-Python-SDK, https://github.com/JetBrains/intellij-community/pull/2591) or have native pixi support themselves.

Pixi itself is already conda compatible (i.e. you can run any conda commands with -p /path/to/.pixi/envs/default). Adding the shim to a default pixi project also requires python to be available in the pixi project (which is not always the case, so we would need to distinguish this case).

Hopefully this is only a "bridge" solution until there is either the possibility for a proper pixi pycharm plugin (afaik it's not possible yet due to the restricted python sdk, happy to be proven wrong) or native pixi support. Not sure how long JetBrains takes for these things to happen (or how much popularity pixi would need to gain), though.