2018-10-16 21:32:16 +01:00
|
|
|
{ stdenv
|
|
|
|
, buildPythonPackage
|
|
|
|
, fetchPypi
|
|
|
|
, gevent
|
|
|
|
}:
|
|
|
|
|
|
|
|
buildPythonPackage rec {
|
|
|
|
pname = "gipc";
|
2020-06-06 07:47:08 +01:00
|
|
|
version = "1.1.0";
|
2018-10-16 21:32:16 +01:00
|
|
|
|
|
|
|
src = fetchPypi {
|
|
|
|
inherit pname version;
|
2020-06-06 07:47:08 +01:00
|
|
|
sha256 = "06116628e9cb7b2c34c8f248d0e4859fa5943e1e07381ad2b234ae9c7ed6f4cc";
|
2018-10-16 21:32:16 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
propagatedBuildInputs = [ gevent ];
|
|
|
|
|
|
|
|
meta = with stdenv.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.
|
|
|
|
'';
|
2020-04-01 02:11:51 +01:00
|
|
|
homepage = "http://gehrcke.de/gipc";
|
2018-10-16 21:32:16 +01:00
|
|
|
license = licenses.mit;
|
2020-11-20 03:53:31 +00:00
|
|
|
# gipc only has support for older versions of gevent
|
|
|
|
broken = versionOlder "1.6" gevent.version;
|
2018-10-16 21:32:16 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
}
|