alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity
nixpkgs/pkgs/development/python-modules/toolz/default.nix

31 lines
639 B
Nix
Raw Normal View History

python.pkgs.toolz: move expression
2017-10-29 11:31:48 +00:00
{ lib
, buildPythonPackage
, fetchPypi
, nose
}:
buildPythonPackage rec{
pname = "toolz";
python: toolz: 0.8.2 -> 0.9.0
2017-12-30 11:28:11 +00:00
version = "0.9.0";
python.pkgs.toolz: move expression
2017-10-29 11:31:48 +00:00
src = fetchPypi {
inherit pname version;
python: toolz: 0.8.2 -> 0.9.0
2017-12-30 11:28:11 +00:00
sha256 = "929f0a7ea7f61c178bd951bdae93920515d3fbdbafc8e6caf82d752b9b3b31c9";
python.pkgs.toolz: move expression
2017-10-29 11:31:48 +00:00
};
checkInputs = [ nose ];
checkPhase = ''
# https://github.com/pytoolz/toolz/issues/357
rm toolz/tests/test_serialization.py
nosetests toolz/tests
'';
python: update documentation This touches up a handful of places in the python documentation to try to make the current best-practices more obvious. In particular, I often find the function signatures (what to pass, what not to pass) confusing and have added them to the docs. Also updated the metas to be more consistent with the most frequently used modern style.
2018-10-10 01:42:29 +01:00
meta = with lib; {
homepage = https://github.com/pytoolz/toolz;
python.pkgs.toolz: move expression
2017-10-29 11:31:48 +00:00
description = "List processing tools and functional utilities";
python: update documentation This touches up a handful of places in the python documentation to try to make the current best-practices more obvious. In particular, I often find the function signatures (what to pass, what not to pass) confusing and have added them to the docs. Also updated the metas to be more consistent with the most frequently used modern style.
2018-10-10 01:42:29 +01:00
license = licenses.bsd3;
maintainers = with maintainers; [ fridh ];
python.pkgs.toolz: move expression
2017-10-29 11:31:48 +00:00
};
treewide: http -> https (#42665)
2018-06-27 21:12:57 +01:00
}
Copy permalink