Python: Difference between revisions
imported>Asymmetric m Remove extra quotes |
imported>Asymmetric m Code highlighting |
||
| Line 17: | Line 17: | ||
Python applications instead should be referenced directly from <code>pkgs/top-level/all-packages.nix</code>. | Python applications instead should be referenced directly from <code>pkgs/top-level/all-packages.nix</code>. | ||
The expression should take | The expression should take <code>pythonPackages</code> as one of the arguments, which guarantees that packages belong to the same set. | ||
= External Documentation = | = External Documentation = | ||
* [https://nixos.org/nixpkgs/manual/#python Python user guide in nixpkgs manual] | * [https://nixos.org/nixpkgs/manual/#python Python user guide in nixpkgs manual] | ||
Revision as of 15:35, 26 February 2018
Contribution guidelines
Libraries
According to the official guidelines for python new package expressions for libraries should be placed in pkgs/development/python-modules/<name>/default.nix. Those expressions are then referenced from pkgs/top-level/python-packages.nix like in this example:
{
aenum = callPackage ../development/python-modules/aenum { };
}
The reasoning behind this is the large size of pkgs/top-level/python-packages.nix. Unfortunately most libraries are still defined in-place in pkgs/top-level/python-packages.nix. If a change to library is necessary or an update is made, it is recommend to move the modified package out of pkgs/top-level/python-packages.nix.
Applications
Python applications instead should be referenced directly from pkgs/top-level/all-packages.nix.
The expression should take pythonPackages as one of the arguments, which guarantees that packages belong to the same set.