From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-exceptiongroup : add recipe
Date: Fri, 17 Jun 2022 14:25:08 +0800 [thread overview]
Message-ID: <1655447108-20329-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1655447108-20329-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/python3-exceptiongroup_1.0.0rc8.bb | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100644 meta/recipes-devtools/python/python3-exceptiongroup_1.0.0rc8.bb
diff --git a/meta/recipes-devtools/python/python3-exceptiongroup_1.0.0rc8.bb b/meta/recipes-devtools/python/python3-exceptiongroup_1.0.0rc8.bb
new file mode 100644
index 0000000000..adf530a6e5
--- /dev/null
+++ b/meta/recipes-devtools/python/python3-exceptiongroup_1.0.0rc8.bb
@@ -0,0 +1,11 @@
+DESCRIPTION = "This is a backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11."
+HOMEPAGE = "https://pypi.org/project/exceptiongroup"
+SECTION = "devel/python"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=d5caa317463c433575efff1d2fe206d7"
+
+SRC_URI[sha256sum] = "6990c24f06b8d33c8065cfe43e5e8a4bfa384e0358be036af9cc60b6321bd11a"
+
+#RDEPENDS:${PN} += "python3-profile python3-logging"
+
+inherit pypi python_setuptools_build_meta
--
2.25.1
next prev parent reply other threads:[~2022-06-17 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 6:25 [OE-core] [PATCH] python3-hypothesis: upgrade 6.46.11 -> 6.47.2 Wang Mingyu
2022-06-17 6:25 ` Wang Mingyu [this message]
2022-06-17 12:17 ` [OE-core] [PATCH] python3-exceptiongroup : add recipe Alexandre Belloni
[not found] ` <16F967959065881B.10812@lists.openembedded.org>
2022-06-17 12:20 ` Alexandre Belloni
2022-06-17 14:08 ` Ross Burton
2022-06-17 14:30 ` Tim Orling
2022-06-18 23:34 ` wangmy
2022-06-17 8:25 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.46.11 -> 6.47.2 Jose Quaresma
2022-06-17 14:33 ` Tim Orling
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=1655447108-20329-2-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-core@lists.openembedded.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