automatic import of python-aiorwlockopeneuler20.03

3 files changed, 107 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..bc3044c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/aiorwlock-1.3.0.tar.gz
diff --git a/python-aiorwlock.spec b/python-aiorwlock.spec
new file mode 100644
index 0000000..2066658
--- /dev/null
+++ b/python-aiorwlock.spec
@@ -0,0 +1,105 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-aiorwlock
+Version:	1.3.0
+Release:	1
+Summary:	Read write lock for asyncio.
+License:	Apache 2
+URL:		https://github.com/aio-libs/aiorwlock
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/77/fe/7027595f5e635ac1f597f7160a420e1f642a474576efb697001efea16bdc/aiorwlock-1.3.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+Read write lock for asyncio_ . A ``RWLock`` maintains a pair of associated
+locks, one for read-only operations and one for writing. The read lock may be
+held simultaneously by multiple reader tasks, so long as there are
+no writers. The write lock is exclusive.
+Whether or not a read-write lock will improve performance over the use of
+a mutual exclusion lock depends on the frequency that the data is *read*
+compared to being *modified*. For example, a collection that is initially
+populated with data and thereafter infrequently modified, while being
+frequently searched is an ideal candidate for the use of a read-write lock.
+However, if updates become frequent then the data spends most of its time
+being exclusively locked and there is little, if any increase in concurrency.
+Implementation is almost direct port from this patch_.
+
+%package -n python3-aiorwlock
+Summary:	Read write lock for asyncio.
+Provides:	python-aiorwlock
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-aiorwlock
+Read write lock for asyncio_ . A ``RWLock`` maintains a pair of associated
+locks, one for read-only operations and one for writing. The read lock may be
+held simultaneously by multiple reader tasks, so long as there are
+no writers. The write lock is exclusive.
+Whether or not a read-write lock will improve performance over the use of
+a mutual exclusion lock depends on the frequency that the data is *read*
+compared to being *modified*. For example, a collection that is initially
+populated with data and thereafter infrequently modified, while being
+frequently searched is an ideal candidate for the use of a read-write lock.
+However, if updates become frequent then the data spends most of its time
+being exclusively locked and there is little, if any increase in concurrency.
+Implementation is almost direct port from this patch_.
+
+%package help
+Summary:	Development documents and examples for aiorwlock
+Provides:	python3-aiorwlock-doc
+%description help
+Read write lock for asyncio_ . A ``RWLock`` maintains a pair of associated
+locks, one for read-only operations and one for writing. The read lock may be
+held simultaneously by multiple reader tasks, so long as there are
+no writers. The write lock is exclusive.
+Whether or not a read-write lock will improve performance over the use of
+a mutual exclusion lock depends on the frequency that the data is *read*
+compared to being *modified*. For example, a collection that is initially
+populated with data and thereafter infrequently modified, while being
+frequently searched is an ideal candidate for the use of a read-write lock.
+However, if updates become frequent then the data spends most of its time
+being exclusively locked and there is little, if any increase in concurrency.
+Implementation is almost direct port from this patch_.
+
+%prep
+%autosetup -n aiorwlock-1.3.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-aiorwlock -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.3.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..62aa830
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+28e4812a1d1d67a2be4370209ece5528  aiorwlock-1.3.0.tar.gz