#80855

Also how come the hash is different from that PR?

@NilsIrl Thanks for noticing, looks like the default output format changed on nix master.

also, this appears to cause a fair number of regression in master, if it's just needed by just one program, you can override the python package set when calling into python. (e.g. for the vimplugin)

also, this appears to cause a fair number of regression in master, if it's just needed by just one program, you can override the python package set when calling into python. (e.g. for the vimplugin)

This is literally the problem Nix is supposed to fix

This is literally the problem Nix is supposed to fix

@NilsIrl this is more or less specific to python, where there's not many good abstractions for introducing/removing visible packages to the python interpreter.

In other words, python doesn't have a patchelf which is able to make executables refer to their exact dependencies.

I was able to determine that all the failures were just noise and merged #80855

unfortunately, the python package set can't really handle many version at the same time. The package set become incoherent if they are present in the same environment. (only one will be imported, and other other will not)

In my original comment, I meant to edit the vimPlugins.deoplete so that the python3 interpreter it has would contain a package set specific to the vim plugin.

Yeah, but that's not a problem except for deep dependencies. That said a single version is easier to maintain.

you can override the python package set when calling into python. (e.g. for the vimplugin)

How would you do that?

https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/python.section.md#overriding-python-packages