automatic import of python-gipc

3 files changed, 122 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..0de6798 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/gipc-1.5.0.tar.gz
diff --git a/python-gipc.spec b/python-gipc.spec
new file mode 100644
index 0000000..9dfc628
--- /dev/null
+++ b/python-gipc.spec
@@ -0,0 +1,120 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-gipc
+Version:	1.5.0
+Release:	1
+Summary:	gevent-cooperative child processes and inter-process communication.
+License:	MIT License
+URL:		https://gehrcke.de/gipc
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/23/cc/d6b4d2f5409db75746f37e4066366cc13217d8109f73595e38779e4896a9/gipc-1.5.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+gipc (pronunciation as in “gipsy”) enables reliable child process management
+and non-blocking inter-process communication in `gevent
+<https://github.com/gevent/gevent>`_-driven software projects.
+Using Python's `multiprocessing package
+<https://docs.python.org/3/library/multiprocessing.html>`_ in the context of a
+codebase that also uses gevent is error-prone and may break the application in
+various `subtle ways
+<https://gehrcke.de/gipc/#what-are-the-challenges-and-what-is-gipc-s-solution>`_.
+With gipc, ``multiprocessing.Process``-based child processes can safely be
+created anywhere within your gevent-powered application. The API of
+``multiprocessing.Process`` objects is provided in a gevent-cooperative way.
+Also, gipc provides a pipe-based transport layer for gevent-cooperative
+inter-greenlet and inter-process communication. gipc is lightweight and easy to
+integrate.
+From 2012 to 2018 gipc's home was at `bitbucket.org/jgehrcke/gipc
+<https://bitbucket.org/jgehrcke/gipc>`_. Since then development has continued on
+GitHub.
+
+%package -n python3-gipc
+Summary:	gevent-cooperative child processes and inter-process communication.
+Provides:	python-gipc
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-gipc
+gipc (pronunciation as in “gipsy”) enables reliable child process management
+and non-blocking inter-process communication in `gevent
+<https://github.com/gevent/gevent>`_-driven software projects.
+Using Python's `multiprocessing package
+<https://docs.python.org/3/library/multiprocessing.html>`_ in the context of a
+codebase that also uses gevent is error-prone and may break the application in
+various `subtle ways
+<https://gehrcke.de/gipc/#what-are-the-challenges-and-what-is-gipc-s-solution>`_.
+With gipc, ``multiprocessing.Process``-based child processes can safely be
+created anywhere within your gevent-powered application. The API of
+``multiprocessing.Process`` objects is provided in a gevent-cooperative way.
+Also, gipc provides a pipe-based transport layer for gevent-cooperative
+inter-greenlet and inter-process communication. gipc is lightweight and easy to
+integrate.
+From 2012 to 2018 gipc's home was at `bitbucket.org/jgehrcke/gipc
+<https://bitbucket.org/jgehrcke/gipc>`_. Since then development has continued on
+GitHub.
+
+%package help
+Summary:	Development documents and examples for gipc
+Provides:	python3-gipc-doc
+%description help
+gipc (pronunciation as in “gipsy”) enables reliable child process management
+and non-blocking inter-process communication in `gevent
+<https://github.com/gevent/gevent>`_-driven software projects.
+Using Python's `multiprocessing package
+<https://docs.python.org/3/library/multiprocessing.html>`_ in the context of a
+codebase that also uses gevent is error-prone and may break the application in
+various `subtle ways
+<https://gehrcke.de/gipc/#what-are-the-challenges-and-what-is-gipc-s-solution>`_.
+With gipc, ``multiprocessing.Process``-based child processes can safely be
+created anywhere within your gevent-powered application. The API of
+``multiprocessing.Process`` objects is provided in a gevent-cooperative way.
+Also, gipc provides a pipe-based transport layer for gevent-cooperative
+inter-greenlet and inter-process communication. gipc is lightweight and easy to
+integrate.
+From 2012 to 2018 gipc's home was at `bitbucket.org/jgehrcke/gipc
+<https://bitbucket.org/jgehrcke/gipc>`_. Since then development has continued on
+GitHub.
+
+%prep
+%autosetup -n gipc-1.5.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-gipc -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 1.5.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..5355315
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+7221ce69fc72c97f801aaed6d37102f3  gipc-1.5.0.tar.gz