I'm requesting this because I ran into a similar issue when trying to install reacton as part of my kernel. It fails to build for similar reasons as pathspec -- it uses hatchling as it's build backend and this results in poetry not adding the package to the flake.lock.
In the linked issue, it was stated that the override solution would be included as part of jupyenv. However, I think that in addition to that, jupyenv should expose an interface for specifying additional nativeBuildInputs.
For example, a nativeBuildInputs which would go inside kernels.nix that would be an attrset of functions that take pythonPackages and return a list of packages.
What's missing?
Related to #442
I'm requesting this because I ran into a similar issue when trying to install
reacton
as part of my kernel. It fails to build for similar reasons aspathspec
-- it useshatchling
as it's build backend and this results inpoetry
not adding the package to the flake.lock.In the linked issue, it was stated that the override solution would be included as part of jupyenv. However, I think that in addition to that, jupyenv should expose an interface for specifying additional
nativeBuildInputs
.For example, a
nativeBuildInputs
which would go insidekernels.nix
that would be an attrset of functions that takepythonPackages
and return a list of packages.Possible solution
No response
Alternatives
No response
Additional context
No response