33afbf39f6
checkInputs used to be added to nativeBuildInputs. Now we have nativeCheckInputs to do that instead. Doing this treewide change allows to keep hashes identical to before the introduction of nativeCheckInputs.
48 lines
1.1 KiB
Nix
48 lines
1.1 KiB
Nix
{ lib
|
|
, buildPythonPackage
|
|
, fetchFromGitHub
|
|
, gevent
|
|
, pytestCheckHook
|
|
}:
|
|
|
|
buildPythonPackage rec {
|
|
pname = "gipc";
|
|
version = "1.4.0";
|
|
format = "setuptools";
|
|
|
|
src = fetchFromGitHub {
|
|
owner = "jgehrcke";
|
|
repo = "gipc";
|
|
rev = "refs/tags/${version}";
|
|
hash = "sha256-T5TqLanODyzJGyjDZz+75bbz3THxoobYnfJFQxAB76E=";
|
|
};
|
|
|
|
postPatch = ''
|
|
substituteInPlace setup.py \
|
|
--replace "gevent>=1.5,<=21.12.0" "gevent>=1.5"
|
|
'';
|
|
|
|
propagatedBuildInputs = [
|
|
gevent
|
|
];
|
|
|
|
nativeCheckInputs = [
|
|
pytestCheckHook
|
|
];
|
|
|
|
meta = with lib; {
|
|
description = "gevent-cooperative child processes and IPC";
|
|
longDescription = ''
|
|
Usage of Python's multiprocessing package in a gevent-powered
|
|
application may raise problems and most likely breaks the application
|
|
in various subtle ways. gipc (pronunciation "gipsy") is developed with
|
|
the motivation to solve many of these issues transparently. With gipc,
|
|
multiprocessing. Process-based child processes can safely be created
|
|
anywhere within your gevent-powered application.
|
|
'';
|
|
homepage = "http://gehrcke.de/gipc";
|
|
license = licenses.mit;
|
|
};
|
|
|
|
}
|