You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most Python library expressions are in python-packages.nix and some are called using callPackage.
We applied makeOverridable to buildPythonPackage so we can override the Python packages. However, callPackage = pkgs.newScope self; also sets a override attribute which is applied later thus taking precedence. We should provide a common method for overriding Python libraries.
Possible methods I can think of:
Define callPackage without providing a override attribute. The override attribute should now correspond to the one added to buildPythonPackage by makeOverridable.
Add a buildPythonPackage.overridePythonPackage method.
I suppose the first would be easiest and the second the most robust.
It would by the way be nice if makeOverridable would allow you to set the attribute used for overriding.
The text was updated successfully, but these errors were encountered:
Issue description
Most Python library expressions are in
python-packages.nix
and some are called usingcallPackage
.We applied
makeOverridable
tobuildPythonPackage
so we can override the Python packages. However,callPackage = pkgs.newScope self;
also sets aoverride
attribute which is applied later thus taking precedence. We should provide a common method for overriding Python libraries.Possible methods I can think of:
callPackage
without providing aoverride
attribute. Theoverride
attribute should now correspond to the one added tobuildPythonPackage
bymakeOverridable
.buildPythonPackage.overridePythonPackage
method.I suppose the first would be easiest and the second the most robust.
It would by the way be nice if
makeOverridable
would allow you to set the attribute used for overriding.The text was updated successfully, but these errors were encountered: