From 94a409450a1773d12b44e0bec40fbd099f9fb883 Mon Sep 17 00:00:00 2001 From: worldofpeace Date: Sun, 24 Mar 2019 05:29:53 -0400 Subject: [PATCH] fixup! doc/python: cleanup examples, references --- doc/languages-frameworks/python.section.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/languages-frameworks/python.section.md b/doc/languages-frameworks/python.section.md index 9cd24d612c5..25b2b728bdf 100644 --- a/doc/languages-frameworks/python.section.md +++ b/doc/languages-frameworks/python.section.md @@ -278,7 +278,7 @@ The following example shows which arguments are given to `buildPythonPackage` in order to build [`datashape`](https://github.com/blaze/datashape). ```nix -{ # ... +{ lib, buildPythonPackage, fetchPypi, numpy, multipledispatch, dateutil, pytest }: buildPythonPackage rec { pname = "datashape"; @@ -312,7 +312,7 @@ Python bindings to `libxml2` and `libxslt`. These libraries are only required when building the bindings and are therefore added as `buildInputs`. ```nix -{ # ... +{ lib, pkgs, buildPythonPackage, fetchPypi }: buildPythonPackage rec { pname = "lxml"; @@ -345,7 +345,7 @@ find each of them in a different folder, and therefore we have to set `LDFLAGS` and `CFLAGS`. ```nix -{ # ... +{ lib, pkgs, buildPythonPackage, fetchPypi, numpy, scipy }: buildPythonPackage rec { pname = "pyFFTW"; @@ -366,7 +366,7 @@ buildPythonPackage rec { preConfigure = '' export LDFLAGS="-L${pkgs.fftw.dev}/lib -L${pkgs.fftwFloat.out}/lib -L${pkgs.fftwLongDouble.out}/lib" export CFLAGS="-I${pkgs.fftw.dev}/include -I${pkgs.fftwFloat.dev}/include -I${pkgs.fftwLongDouble.dev}/include" - ''; + ''; meta = with lib; { description = "A pythonic wrapper around FFTW, the FFT library, presenting a unified interface for all the supported transforms";