From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-cython: upgrade 0.29.33 -> 0.29.34
Date: Mon, 10 Apr 2023 17:37:17 +0800 [thread overview]
Message-ID: <1681119440-25219-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1681119440-25219-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Bugs fixed
==========
- A refence leak of the for-loop list/tuple iterable was resolved if the
for-loop's else: branch executes a break for an outer loop.
- Some C compile failures in CPython 3.12 were resolved.
- Some old usages of the deprecated Python imp module were replaced with importlib.
- Some issues with depfile generation were resolved.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-devtools/python/python-cython.inc | 2 +-
.../{python3-cython_0.29.33.bb => python3-cython_0.29.34.bb} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-cython_0.29.33.bb => python3-cython_0.29.34.bb} (100%)
diff --git a/meta/recipes-devtools/python/python-cython.inc b/meta/recipes-devtools/python/python-cython.inc
index 30d1b39467..2b778493cd 100644
--- a/meta/recipes-devtools/python/python-cython.inc
+++ b/meta/recipes-devtools/python/python-cython.inc
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=e23fadd6ceef8c618fc1c65191d846fa"
PYPI_PACKAGE = "Cython"
BBCLASSEXTEND = "native nativesdk"
-SRC_URI[sha256sum] = "5040764c4a4d2ce964a395da24f0d1ae58144995dab92c6b96f44c3f4d72286a"
+SRC_URI[sha256sum] = "1909688f5d7b521a60c396d20bba9e47a1b2d2784bfb085401e1e1e7d29a29a8"
UPSTREAM_CHECK_REGEX = "Cython-(?P<pver>.*)\.tar"
inherit pypi
diff --git a/meta/recipes-devtools/python/python3-cython_0.29.33.bb b/meta/recipes-devtools/python/python3-cython_0.29.34.bb
similarity index 100%
rename from meta/recipes-devtools/python/python3-cython_0.29.33.bb
rename to meta/recipes-devtools/python/python3-cython_0.29.34.bb
--
2.34.1
next prev parent reply other threads:[~2023-04-10 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 9:37 [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 wangmy
2023-04-10 9:37 ` wangmy [this message]
2023-04-10 9:37 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.68.2 -> 6.71.0 wangmy
2023-04-10 9:37 ` [OE-core] [PATCH] python3-importlib-metadata: upgrade 6.0.0 -> 6.2.0 wangmy
2023-04-10 9:37 ` [OE-core] [PATCH] zstd: upgrade 1.5.4 -> 1.5.5 wangmy
2023-04-12 7:35 ` Luca Ceresoli
2023-04-10 16:17 ` [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 Tim Orling
2023-04-10 17:25 ` Alexandre Belloni
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=1681119440-25219-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