Python: Difference between revisions
imported>Krey |
imported>Mic92 No edit summary |
||
| Line 29: | Line 29: | ||
Add <code>virtualenvwrapper</code> to your list of Python packages above. You can use pip safely inside such a virtualenv, most pure Python packages should work. | Add <code>virtualenvwrapper</code> to your list of Python packages above. You can use pip safely inside such a virtualenv, most pure Python packages should work. | ||
<syntaxhighlight lang=" | <syntaxhighlight lang="console"> | ||
virtualenv my-new-python-venv | $ virtualenv my-new-python-venv | ||
source my-new-python-venv/bin/activate | $ source my-new-python-venv/bin/activate | ||
pip install pandas_datareader # or some other package you want | $ pip install pandas_datareader # or some other package you want | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 22:12, 10 March 2018
Installation
The Python packages available to the interpreter must be declared when installing Python.
Supposing you want Python 3 with pandas and requests, then configuration.nix should then look something like
environment.systemPackages =
let myPythonPackages = pythonPackages: with pythonPackages; [
pandas
requests
# other python packages you want
];
in
with pkgs; [
(python3.withPackages myPythonPackages)
# all your other (non-Python) packages
]
There are several versions of Python available. Replace python3 with python2 or pypy in the above snippet according to your needs.
Explanation (optional)
We defined a function myPythonPackages which takes as input a set pythonPackages and returns a list of attributes thereof.
Dealing with missing/outdated packages
Add virtualenvwrapper to your list of Python packages above. You can use pip safely inside such a virtualenv, most pure Python packages should work.
$ virtualenv my-new-python-venv
$ source my-new-python-venv/bin/activate
$ pip install pandas_datareader # or some other package you want
This, of course, goes against the declarative nature of the rest of the configuration and should be avoided if possible.
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. For example:
{ lib
, pythonPackages
}:
with pythonPackages;
buildPythonApplication rec {
# ...