From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/rustworkx/
Date: Sun, 30 Oct 2022 20:42:43 +0000 (UTC) [thread overview]
Message-ID: <1667162552.c7df5e0dc6e3b19e28457d75a964703292e961e9.sam@gentoo> (raw)
commit: c7df5e0dc6e3b19e28457d75a964703292e961e9
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 30 20:42:32 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct 30 20:42:32 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c7df5e0d
dev-python/rustworkx: update upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/rustworkx/metadata.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-python/rustworkx/metadata.xml b/dev-python/rustworkx/metadata.xml
index 2c287d8e177b..5025a8788f35 100644
--- a/dev-python/rustworkx/metadata.xml
+++ b/dev-python/rustworkx/metadata.xml
@@ -14,10 +14,10 @@
<name>Proxy Maintainers</name>
</maintainer>
<longdescription>
- retworkx is a general purpose graph library for python3 written in Rust to take advantage of the performance and safety that Rust provides. It was built as a replacement for qiskit's previous (and current) networkx usage (hence the name) but is designed to provide a high performance general purpose graph library for any python application. The project was originally started to build a faster directed graph to use as the underlying data structure for the DAG at the center of qiskit-terra's transpiler, but it has since grown to cover all the graph usage in Qiskit and other applications.
+ rustworkx is a general purpose graph library for python3 written in Rust to take advantage of the performance and safety that Rust provides. It was built as a replacement for qiskit's previous (and current) networkx usage (hence the name) but is designed to provide a high performance general purpose graph library for any python application. The project was originally started to build a faster directed graph to use as the underlying data structure for the DAG at the center of qiskit-terra's transpiler, but it has since grown to cover all the graph usage in Qiskit and other applications.
</longdescription>
<upstream>
- <remote-id type="github">Qiskit/retworkx</remote-id>
- <remote-id type="pypi">retworkx</remote-id>
+ <remote-id type="github">Qiskit/rustworkx</remote-id>
+ <remote-id type="pypi">rustworkx</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2022-10-30 20:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 20:42 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-26 15:08 [gentoo-commits] repo/gentoo:master commit in: dev-python/rustworkx/ Michał Górny
2023-01-27 20:10 Michał Górny
2023-05-04 16:56 Michał Górny
2023-06-07 14:37 Sam James
2023-06-18 19:01 Michał Górny
2023-06-18 19:01 Michał Górny
2023-08-01 3:01 Michał Górny
2023-10-04 5:51 Michał Górny
2023-11-08 15:48 Michał Górny
2023-11-08 15:48 Michał Górny
2024-01-24 6:33 Michał Górny
2024-02-23 3:40 Michał Górny
2024-02-26 14:25 Michał Górny
2024-03-13 6:51 Michał Górny
2024-05-12 13:05 Michał Górny
2024-06-28 4:23 Michał Górny
2024-06-29 2:57 Michał Górny
2024-07-07 17:23 Michał Górny
2024-07-12 16:10 Michał Górny
2024-07-12 16:10 Michał Górny
2024-08-17 4:51 Michał Górny
2024-08-17 4:51 Michał Górny
2025-01-24 7:21 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=1667162552.c7df5e0dc6e3b19e28457d75a964703292e961e9.sam@gentoo \
--to=sam@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