summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-03-09 17:39:19 +0000
committerCoprDistGit <infra@openeuler.org>2023-03-09 17:39:19 +0000
commit2f58b14052b5c0d381bb6570abfa1d81f690e388 (patch)
tree6f73dabe310817ff696fd5ae6437b22002545624
parentfa809ed78e0c6dad37b8454fe3d9279e2afd2e57 (diff)
automatic import of python-trio
-rw-r--r--.gitignore1
-rw-r--r--python-trio.spec269
-rw-r--r--sources1
3 files changed, 271 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..78277af 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/trio-0.22.0.tar.gz
diff --git a/python-trio.spec b/python-trio.spec
new file mode 100644
index 0000000..2230928
--- /dev/null
+++ b/python-trio.spec
@@ -0,0 +1,269 @@
+%global _empty_manifest_terminate_build 0
+Name: python-trio
+Version: 0.22.0
+Release: 1
+Summary: A friendly Python library for async concurrency and I/O
+License: MIT OR Apache-2.0
+URL: https://github.com/python-trio/trio
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/0b/b8/1b81d2149c3e2c25900d40b8e6c8d3ca502a3cc844b90c962b0854aaf3f3/trio-0.22.0.tar.gz
+BuildArch: noarch
+
+Requires: python3-attrs
+Requires: python3-sortedcontainers
+Requires: python3-async-generator
+Requires: python3-idna
+Requires: python3-outcome
+Requires: python3-sniffio
+Requires: python3-cffi
+Requires: python3-exceptiongroup
+
+%description
+.. image:: https://raw.githubusercontent.com/python-trio/trio/9b0bec646a31e0d0f67b8b6ecc6939726faf3e17/logo/logo-with-background.svg
+ :width: 200px
+ :align: right
+
+The Trio project's goal is to produce a production-quality, `permissively
+licensed <https://github.com/python-trio/trio/blob/master/LICENSE>`__,
+async/await-native I/O library for Python. Like all async libraries,
+its main purpose is to help you write programs that do **multiple
+things at the same time** with **parallelized I/O**. A web spider that
+wants to fetch lots of pages in parallel, a web server that needs to
+juggle lots of downloads and websocket connections at the same time, a
+process supervisor monitoring multiple subprocesses... that sort of
+thing. Compared to other libraries, Trio attempts to distinguish
+itself with an obsessive focus on **usability** and
+**correctness**. Concurrency is complicated; we try to make it *easy*
+to get things *right*.
+
+Trio was built from the ground up to take advantage of the `latest
+Python features <https://www.python.org/dev/peps/pep-0492/>`__, and
+draws inspiration from `many sources
+<https://github.com/python-trio/trio/wiki/Reading-list>`__, in
+particular Dave Beazley's `Curio <https://curio.readthedocs.io/>`__.
+The resulting design is radically simpler than older competitors like
+`asyncio <https://docs.python.org/3/library/asyncio.html>`__ and
+`Twisted <https://twistedmatrix.com/>`__, yet just as capable. Trio is
+the Python I/O library I always wanted; I find it makes building
+I/O-oriented programs easier, less error-prone, and just plain more
+fun. `Perhaps you'll find the same
+<https://github.com/python-trio/trio/wiki/Testimonials>`__.
+
+This project is young and still somewhat experimental: the overall
+design is solid and the existing features are fully tested and
+documented, but you may encounter missing functionality or rough
+edges. We *do* encourage you do use it, but you should `read and
+subscribe to issue #1
+<https://github.com/python-trio/trio/issues/1>`__ to get warning and a
+chance to give feedback about any compatibility-breaking changes.
+
+Vital statistics:
+
+* Supported environments: Linux, macOS, or Windows running some kind of Python
+ 3.7-or-better (either CPython or PyPy3 is fine). \*BSD and illumos likely
+ work too, but are not tested.
+
+* Install: ``python3 -m pip install -U trio`` (or on Windows, maybe
+ ``py -3 -m pip install -U trio``). No compiler needed.
+
+* Tutorial and reference manual: https://trio.readthedocs.io
+
+* Bug tracker and source code: https://github.com/python-trio/trio
+
+* Real-time chat: https://gitter.im/python-trio/general
+
+* Discussion forum: https://trio.discourse.group
+
+* License: MIT or Apache 2, your choice
+
+* Contributor guide: https://trio.readthedocs.io/en/latest/contributing.html
+
+* Code of conduct: Contributors are requested to follow our `code of
+ conduct
+ <https://trio.readthedocs.io/en/latest/code-of-conduct.html>`_
+ in all project spaces.
+
+
+%package -n python3-trio
+Summary: A friendly Python library for async concurrency and I/O
+Provides: python-trio
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-trio
+.. image:: https://raw.githubusercontent.com/python-trio/trio/9b0bec646a31e0d0f67b8b6ecc6939726faf3e17/logo/logo-with-background.svg
+ :width: 200px
+ :align: right
+
+The Trio project's goal is to produce a production-quality, `permissively
+licensed <https://github.com/python-trio/trio/blob/master/LICENSE>`__,
+async/await-native I/O library for Python. Like all async libraries,
+its main purpose is to help you write programs that do **multiple
+things at the same time** with **parallelized I/O**. A web spider that
+wants to fetch lots of pages in parallel, a web server that needs to
+juggle lots of downloads and websocket connections at the same time, a
+process supervisor monitoring multiple subprocesses... that sort of
+thing. Compared to other libraries, Trio attempts to distinguish
+itself with an obsessive focus on **usability** and
+**correctness**. Concurrency is complicated; we try to make it *easy*
+to get things *right*.
+
+Trio was built from the ground up to take advantage of the `latest
+Python features <https://www.python.org/dev/peps/pep-0492/>`__, and
+draws inspiration from `many sources
+<https://github.com/python-trio/trio/wiki/Reading-list>`__, in
+particular Dave Beazley's `Curio <https://curio.readthedocs.io/>`__.
+The resulting design is radically simpler than older competitors like
+`asyncio <https://docs.python.org/3/library/asyncio.html>`__ and
+`Twisted <https://twistedmatrix.com/>`__, yet just as capable. Trio is
+the Python I/O library I always wanted; I find it makes building
+I/O-oriented programs easier, less error-prone, and just plain more
+fun. `Perhaps you'll find the same
+<https://github.com/python-trio/trio/wiki/Testimonials>`__.
+
+This project is young and still somewhat experimental: the overall
+design is solid and the existing features are fully tested and
+documented, but you may encounter missing functionality or rough
+edges. We *do* encourage you do use it, but you should `read and
+subscribe to issue #1
+<https://github.com/python-trio/trio/issues/1>`__ to get warning and a
+chance to give feedback about any compatibility-breaking changes.
+
+Vital statistics:
+
+* Supported environments: Linux, macOS, or Windows running some kind of Python
+ 3.7-or-better (either CPython or PyPy3 is fine). \*BSD and illumos likely
+ work too, but are not tested.
+
+* Install: ``python3 -m pip install -U trio`` (or on Windows, maybe
+ ``py -3 -m pip install -U trio``). No compiler needed.
+
+* Tutorial and reference manual: https://trio.readthedocs.io
+
+* Bug tracker and source code: https://github.com/python-trio/trio
+
+* Real-time chat: https://gitter.im/python-trio/general
+
+* Discussion forum: https://trio.discourse.group
+
+* License: MIT or Apache 2, your choice
+
+* Contributor guide: https://trio.readthedocs.io/en/latest/contributing.html
+
+* Code of conduct: Contributors are requested to follow our `code of
+ conduct
+ <https://trio.readthedocs.io/en/latest/code-of-conduct.html>`_
+ in all project spaces.
+
+
+%package help
+Summary: Development documents and examples for trio
+Provides: python3-trio-doc
+%description help
+.. image:: https://raw.githubusercontent.com/python-trio/trio/9b0bec646a31e0d0f67b8b6ecc6939726faf3e17/logo/logo-with-background.svg
+ :width: 200px
+ :align: right
+
+The Trio project's goal is to produce a production-quality, `permissively
+licensed <https://github.com/python-trio/trio/blob/master/LICENSE>`__,
+async/await-native I/O library for Python. Like all async libraries,
+its main purpose is to help you write programs that do **multiple
+things at the same time** with **parallelized I/O**. A web spider that
+wants to fetch lots of pages in parallel, a web server that needs to
+juggle lots of downloads and websocket connections at the same time, a
+process supervisor monitoring multiple subprocesses... that sort of
+thing. Compared to other libraries, Trio attempts to distinguish
+itself with an obsessive focus on **usability** and
+**correctness**. Concurrency is complicated; we try to make it *easy*
+to get things *right*.
+
+Trio was built from the ground up to take advantage of the `latest
+Python features <https://www.python.org/dev/peps/pep-0492/>`__, and
+draws inspiration from `many sources
+<https://github.com/python-trio/trio/wiki/Reading-list>`__, in
+particular Dave Beazley's `Curio <https://curio.readthedocs.io/>`__.
+The resulting design is radically simpler than older competitors like
+`asyncio <https://docs.python.org/3/library/asyncio.html>`__ and
+`Twisted <https://twistedmatrix.com/>`__, yet just as capable. Trio is
+the Python I/O library I always wanted; I find it makes building
+I/O-oriented programs easier, less error-prone, and just plain more
+fun. `Perhaps you'll find the same
+<https://github.com/python-trio/trio/wiki/Testimonials>`__.
+
+This project is young and still somewhat experimental: the overall
+design is solid and the existing features are fully tested and
+documented, but you may encounter missing functionality or rough
+edges. We *do* encourage you do use it, but you should `read and
+subscribe to issue #1
+<https://github.com/python-trio/trio/issues/1>`__ to get warning and a
+chance to give feedback about any compatibility-breaking changes.
+
+Vital statistics:
+
+* Supported environments: Linux, macOS, or Windows running some kind of Python
+ 3.7-or-better (either CPython or PyPy3 is fine). \*BSD and illumos likely
+ work too, but are not tested.
+
+* Install: ``python3 -m pip install -U trio`` (or on Windows, maybe
+ ``py -3 -m pip install -U trio``). No compiler needed.
+
+* Tutorial and reference manual: https://trio.readthedocs.io
+
+* Bug tracker and source code: https://github.com/python-trio/trio
+
+* Real-time chat: https://gitter.im/python-trio/general
+
+* Discussion forum: https://trio.discourse.group
+
+* License: MIT or Apache 2, your choice
+
+* Contributor guide: https://trio.readthedocs.io/en/latest/contributing.html
+
+* Code of conduct: Contributors are requested to follow our `code of
+ conduct
+ <https://trio.readthedocs.io/en/latest/code-of-conduct.html>`_
+ in all project spaces.
+
+
+%prep
+%autosetup -n trio-0.22.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-trio -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 0.22.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..a417d67
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+f7dbfa6a8722065f09da188641d8ed93 trio-0.22.0.tar.gz