316de025d1
While the version listed on PyPI is "0.4.0.final.0", the actual tarball
however is called just "meliae-0.4.0.tar.gz", which is the same *name*
(but different hash) as the one before the update in
7ce848309e
.
Here is the PyPI page for reference:
https://pypi.python.org/pypi/meliae/0.4.0.final.0
After checking the tarballs contents, the version string however *is*
"0.4.0.final.0", so I'm only changing the version in the download URL
rather than in the version attribute.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @FRidh
43 lines
902 B
Nix
43 lines
902 B
Nix
{ stdenv
|
|
, buildPythonPackage
|
|
, fetchPypi
|
|
, cython
|
|
, isPy3k
|
|
, simplejson
|
|
}:
|
|
|
|
buildPythonPackage rec {
|
|
pname = "meliae";
|
|
version = "0.4.0.final.0";
|
|
name = "${pname}-${version}";
|
|
|
|
src = fetchPypi {
|
|
inherit pname;
|
|
# FIXME when updating to the next version: The tarball on pypi is called
|
|
# "meliae-0.4.0.tar.gz" while the version within that tarball is
|
|
# "0.4.0.final.0".
|
|
version = "0.4.0";
|
|
sha256 = "976519ab02aaa6a8fb5f596dc4dd9f64fc9510b00e054979566e51c9be7cec99";
|
|
};
|
|
|
|
disabled = isPy3k;
|
|
|
|
doCheck = true;
|
|
|
|
checkPhase = ''
|
|
python setup.py build_ext -i
|
|
python run_tests.py
|
|
'';
|
|
|
|
checkInputs = [ simplejson ];
|
|
|
|
propagatedBuildInputs = [ cython ];
|
|
|
|
meta = with stdenv.lib; {
|
|
description = "Python Memory Usage Analyzer";
|
|
homepage = http://launchpad.net/meliae;
|
|
license = licenses.gpl3;
|
|
maintainers = with maintainers; [ xvapx ];
|
|
};
|
|
}
|