b12f/nixpkgs
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

doc: cleanup whitespace in python.md

Browse source
This commit is contained in:
Alexey Muranov 2017-03-05 01:00:02 +01:00 committed by Jörg Thalheim
parent c1c624f077
commit 97c9ed0ba1
No known key found for this signature in database
GPG key ID: CA4106B8D7CC79FA
1 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/languages-frameworks/python.md
View file

@ -576,7 +576,7 @@ specified packages in its path.
#### python.withPackages function #### python.withPackages function
The `python.withPackages` function provides a simpler interface to the `python.buildEnv` functionality. The `python.withPackages` function provides a simpler interface to the `python.buildEnv` functionality.
It takes a function as an argument that is passed the set of python packages and returns the list It takes a function as an argument that is passed the set of python packages and returns the list
of the packages to be included in the environment. Using the `withPackages` function, the previous of the packages to be included in the environment. Using the `withPackages` function, the previous
example for the Pyramid Web Framework environment can be written like this: example for the Pyramid Web Framework environment can be written like this:
@ -584,10 +584,10 @@ example for the Pyramid Web Framework environment can be written like this:
python.withPackages (ps: [ps.pyramid]) python.withPackages (ps: [ps.pyramid])
`withPackages` passes the correct package set for the specific interpreter version as an `withPackages` passes the correct package set for the specific interpreter version as an
argument to the function. In the above example, `ps` equals `pythonPackages`. argument to the function. In the above example, `ps` equals `pythonPackages`.
But you can also easily switch to using python3: But you can also easily switch to using python3:
with import <nixpkgs> {}; with import <nixpkgs> {};
python3.withPackages (ps: [ps.pyramid]) python3.withPackages (ps: [ps.pyramid])
@ -828,7 +828,7 @@ Create this `default.nix` file, together with a `requirements.txt` and simply ex
with import <nixpkgs> {}; with import <nixpkgs> {};
with pkgs.python27Packages; with pkgs.python27Packages;
stdenv.mkDerivation { stdenv.mkDerivation {
name = "impurePythonEnv"; name = "impurePythonEnv";
buildInputs = [ buildInputs = [
# these packages are required for virtualenv and pip to work: # these packages are required for virtualenv and pip to work:
@ -836,10 +836,10 @@ stdenv.mkDerivation {
python27Full python27Full
python27Packages.virtualenv python27Packages.virtualenv
python27Packages.pip python27Packages.pip
# the following packages are related to the dependencies of your python # the following packages are related to the dependencies of your python
# project. # project.
# In this particular example the python modules listed in the # In this particular example the python modules listed in the
# requirements.tx require the following packages to be installed locally # requirements.tx require the following packages to be installed locally
# in order to compile any binary extensions they may require. # in order to compile any binary extensions they may require.
# #
taglib taglib
@ -854,7 +854,7 @@ stdenv.mkDerivation {
shellHook = '' shellHook = ''
# set SOURCE_DATE_EPOCH so that we can use python wheels # set SOURCE_DATE_EPOCH so that we can use python wheels
SOURCE_DATE_EPOCH=$(date +%s) SOURCE_DATE_EPOCH=$(date +%s)
virtualenv --no-setuptools venv virtualenv --no-setuptools venv
export PATH=$PWD/venv/bin:$PATH export PATH=$PWD/venv/bin:$PATH
pip install -r requirements.txt pip install -r requirements.txt
''; '';
@ -862,7 +862,7 @@ stdenv.mkDerivation {
``` ```
Note that the `pip install` is an imperative action. So every time `nix-shell` Note that the `pip install` is an imperative action. So every time `nix-shell`
is executed it will attempt to download the python modules listed in is executed it will attempt to download the python modules listed in
requirements.txt. However these will be cached locally within the `virtualenv` requirements.txt. However these will be cached locally within the `virtualenv`
folder and not downloaded again. folder and not downloaded again.