From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/trio/
Date: Sun, 27 Jun 2021 11:23:10 +0000 (UTC) [thread overview]
Message-ID: <1624792267.46913cc7e7f4c6574f7c0b3fb7aa5c5a7acdfcbd.andrewammerlaan@gentoo> (raw)
commit: 46913cc7e7f4c6574f7c0b3fb7aa5c5a7acdfcbd
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 27 11:11:07 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Sun Jun 27 11:11:07 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46913cc7
dev-python/trio: import from ::guru
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
dev-python/trio/Manifest | 1 +
dev-python/trio/metadata.xml | 21 +++++++++++++++
dev-python/trio/trio-0.19.0.ebuild | 54 ++++++++++++++++++++++++++++++++++++++
3 files changed, 76 insertions(+)
diff --git a/dev-python/trio/Manifest b/dev-python/trio/Manifest
new file mode 100644
index 00000000000..3a72c2dee33
--- /dev/null
+++ b/dev-python/trio/Manifest
@@ -0,0 +1 @@
+DIST trio-0.19.0.tar.gz 486036 BLAKE2B 052cadb8d251960b20349659b92f4d26c5b65128cbbfafee21a4a4b90463e43d9c9db6b35f3659d2b062c7d0b8b8914b31b38d2faed6c9d948c0ccbe85a0a250 SHA512 5297a3f48b786eac05b686f1e8bb0603a9c0133d6c4872a307cdc8f1e37aedb57d668b61c2568c82b7d1058b6604a22d2c5c2298f13d13f0daf8e9259aa76d7c
diff --git a/dev-python/trio/metadata.xml b/dev-python/trio/metadata.xml
new file mode 100644
index 00000000000..1bb5fd59d25
--- /dev/null
+++ b/dev-python/trio/metadata.xml
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+ <maintainer type="person">
+ <email>andrewammerlaan@gentoo.org</email>
+ <name>Andrew Ammerlaan</name>
+ </maintainer>
+ <stabilize-allarches/>
+ <longdescription lang="en">
+The Trio project's goal is to produce a production-quality, permissively licensed, 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, and draws inspiration from many sources, in particular Dave Beazley's Curio. The resulting design is radically simpler than older competitors like asyncio and Twisted, 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.
+
+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 to use it, but you should read and subscribe to issue #1 to get warning and a chance to give feedback about any compatibility-breaking changes.
+ </longdescription>
+ <upstream>
+ <remote-id type="github">python-trio/trio</remote-id>
+ <remote-id type="pypi">trio</remote-id>
+ </upstream>
+</pkgmetadata>
diff --git a/dev-python/trio/trio-0.19.0.ebuild b/dev-python/trio/trio-0.19.0.ebuild
new file mode 100644
index 00000000000..14417d4fa8a
--- /dev/null
+++ b/dev-python/trio/trio-0.19.0.ebuild
@@ -0,0 +1,54 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{8..9} )
+
+inherit distutils-r1
+
+DESCRIPTION="Python library for async concurrency and I/O"
+HOMEPAGE="
+ https://github.com/python-trio/trio
+ https://pypi.org/project/trio
+"
+SRC_URI="https://github.com/python-trio/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="|| ( Apache-2.0 MIT )"
+SLOT="0"
+KEYWORDS="~amd64"
+
+RDEPEND="
+ >=dev-python/async_generator-1.9[${PYTHON_USEDEP}]
+ >=dev-python/attrs-19.2.0[${PYTHON_USEDEP}]
+ dev-python/idna[${PYTHON_USEDEP}]
+ dev-python/outcome[${PYTHON_USEDEP}]
+ dev-python/sniffio[${PYTHON_USEDEP}]
+ dev-python/sortedcontainers[${PYTHON_USEDEP}]
+"
+BDEPEND="
+ test? (
+ >=dev-python/astor-0.8.0[${PYTHON_USEDEP}]
+ >=dev-python/immutables-0.6[${PYTHON_USEDEP}]
+ dev-python/ipython[${PYTHON_USEDEP}]
+ >=dev-python/jedi-0.18.0[${PYTHON_USEDEP}]
+ dev-python/pyopenssl[${PYTHON_USEDEP}]
+ dev-python/pylint[${PYTHON_USEDEP}]
+ dev-python/trustme[${PYTHON_USEDEP}]
+ )
+"
+
+distutils_enable_tests --install pytest
+distutils_enable_sphinx docs/source \
+ dev-python/immutables \
+ dev-python/sphinxcontrib-trio \
+ dev-python/sphinx_rtd_theme \
+ dev-python/towncrier
+
+python_prepare_all() {
+ # these tests require internet access
+ rm trio/tests/test_ssl.py || die
+ rm trio/tests/test_highlevel_ssl_helpers.py || die
+
+ distutils-r1_python_prepare_all
+}
next reply other threads:[~2021-06-27 11:23 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 11:23 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-12 21:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/trio/ Sam James
2021-07-12 22:11 Sam James
2021-07-17 4:39 Sam James
2021-07-24 15:22 Sam James
2021-08-17 17:15 Marek Szuba
2021-08-30 1:27 Sam James
2021-08-30 7:26 Agostino Sarubbo
2021-08-31 17:39 Sam James
2021-09-04 21:39 Sam James
2021-09-25 16:37 Sam James
2021-11-14 8:30 Sam James
2021-11-18 9:09 Sam James
2021-11-19 6:41 Sam James
2021-11-27 13:46 Michał Górny
2021-11-27 13:46 Michał Górny
2022-02-21 19:09 Andrew Ammerlaan
2022-03-26 17:00 Arthur Zamarin
2022-03-26 18:00 Arthur Zamarin
2022-03-26 18:20 Arthur Zamarin
2022-03-26 18:20 Arthur Zamarin
2022-04-07 8:45 Michał Górny
2022-04-07 8:45 Michał Górny
2022-04-07 8:45 Michał Górny
2022-04-07 8:45 Michał Górny
2022-04-07 8:45 Michał Górny
2022-04-07 8:45 Michał Górny
2022-04-25 17:16 Sam James
2022-05-06 13:22 Michał Górny
2022-06-08 5:35 Michał Górny
2022-07-10 16:56 Sam James
2022-09-28 13:13 Andrew Ammerlaan
2022-11-03 19:38 Arthur Zamarin
2022-11-04 6:13 Michał Górny
2022-11-26 15:40 Michał Górny
2023-03-16 18:13 Michał Górny
2023-05-30 16:18 Michał Górny
2023-05-30 16:18 Michał Górny
2023-06-08 5:13 Michał Górny
2023-07-03 4:15 Michał Górny
2023-07-09 16:51 Arthur Zamarin
2023-07-10 1:47 Michał Górny
2023-07-13 5:28 Michał Górny
2023-08-02 16:37 Sam James
2023-08-02 18:52 Michał Górny
2023-11-03 7:06 Michał Górny
2023-11-04 17:14 Arthur Zamarin
2023-11-10 13:35 Andrew Ammerlaan
2023-11-29 10:21 Michał Górny
2023-11-29 10:26 Michał Górny
2023-12-14 13:58 Michał Górny
2023-12-30 14:28 Arthur Zamarin
2023-12-30 14:40 Michał Górny
2024-01-10 4:42 Michał Górny
2024-01-24 18:59 Michał Górny
2024-01-24 19:05 Michał Górny
2024-03-17 16:41 Michał Górny
2024-04-06 9:32 Arthur Zamarin
2024-05-16 15:28 Michał Górny
2024-06-01 7:10 Arthur Zamarin
2024-06-01 7:22 Michał Górny
2024-06-14 15:55 Michał Górny
2024-07-05 9:42 Andrew Ammerlaan
2024-07-20 7:39 Arthur Zamarin
2024-07-20 9:01 Michał Górny
2024-08-05 11:48 Michał Górny
2024-08-08 3:08 Michał Górny
2024-08-24 8:18 Sam James
2024-08-24 13:06 Michał Górny
2024-10-17 2:51 Michał Górny
2024-11-02 8:49 Michał Górny
2024-11-02 8:59 Michał Górny
2024-12-26 7:50 Michał Górny
2025-01-11 9:05 Sam James
2025-01-11 9:36 Michał Górny
2025-02-15 7:01 Michał Górny
2025-02-16 18:44 Michał Górny
2025-03-01 11:57 Michał Górny
2025-05-14 11:59 Michał Górny
2025-05-19 14:53 Nowa Ammerlaan
2025-05-20 17:17 Michał Górny
2025-06-07 10:01 Arthur Zamarin
2025-06-07 10:22 Michał Górny
2025-09-10 6:04 Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1624792267.46913cc7e7f4c6574f7c0b3fb7aa5c5a7acdfcbd.andrewammerlaan@gentoo \
--to=andrewammerlaan@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox