From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/trio/
Date: Mon, 24 May 2021 11:06:40 +0000 (UTC) [thread overview]
Message-ID: <1621850380.0b8259a44785eeb8e45b4335f26d1e883dc2efc8.andrewammerlaan@gentoo> (raw)
Message-ID: <20210524110640.gp5nXOddLolElksfmXc7Y_tr3XMp_P_4wkONfnrplUk@z> (raw)
commit: 0b8259a44785eeb8e45b4335f26d1e883dc2efc8
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Mon May 24 09:42:40 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Mon May 24 09:59:40 2021 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=0b8259a4
dev-python/trio: <!-- maintainer-needed -->
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
dev-python/trio/metadata.xml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/dev-python/trio/metadata.xml b/dev-python/trio/metadata.xml
index d086a391f..dcb4e4c82 100644
--- a/dev-python/trio/metadata.xml
+++ b/dev-python/trio/metadata.xml
@@ -2,10 +2,7 @@
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>andrewammerlaan@gentoo.org</email>
- <name>Andrew Ammerlaan</name>
- </maintainer>
+ <!-- maintainer-needed -->
<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.
next reply other threads:[~2021-05-24 11:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 10:01 Andrew Ammerlaan [this message]
2021-05-24 11:06 ` [gentoo-commits] repo/proj/guru:master commit in: dev-python/trio/ Andrew Ammerlaan
-- strict thread matches above, loose matches on Subject: below --
2021-04-19 14:52 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-04-13 12:27 Andrew Ammerlaan
2021-02-17 17:59 Andrew Ammerlaan
2021-01-24 10:21 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-01-24 10:21 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-11-28 13:57 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-11-28 13:46 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-11-27 10:26 Alessandro Barbieri
2020-10-18 9:03 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-10-18 9:03 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-29 14:14 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-08-29 14:14 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-29 14:14 Andrew Ammerlaan
2020-06-15 11:35 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-06-15 11:34 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-06-15 11:34 Andrew Ammerlaan
2020-05-24 19:03 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-05-24 8:35 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-05-06 17:14 Andrew Ammerlaan
2020-03-31 15:26 Alessandro Barbieri
2020-03-29 13:21 Andrew Ammerlaan
2020-03-27 17:52 Alessandro Barbieri
2020-03-09 15:35 Andrew Ammerlaan
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=1621850380.0b8259a44785eeb8e45b4335f26d1e883dc2efc8.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