From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/5] python3-pyparsing: upgrade 3.3.2 -> 3.3.3
Date: Mon, 21 Sep 2026 15:58:33 +0100 [thread overview]
Message-ID: <20260921145835.1106731-3-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260921145835.1106731-1-richard.purdie@linuxfoundation.org>
Version 3.3.3 - September, 2026
-------------------------------
- Added support for Python 3.15.
- Fixed CI unit test jobs selecting a tox environment with no test commands.
The matrix and fallback now select `py-unit`, as diagnosed and proposed by
glaziermag in issue #662; submitted by Neal Lin et AI.
- Refactored recursive implementations in pyparsing, for improved performance and
reduced memory usage.
- repetition using a large upper bound with multiplication or slicing notation
has replaced a recursive `Optional` expression with a modified `ZeroOrMore`
expression, using a new `max` argument. PR #652, submitted by sudo.
- `nested_expr` now uses an internal class that maintains its own stack for
managing nesting levels.
- `infix_notation` replaced its recursive implementation with a shunting-yard
algorithm.
These changes should not cause any regressions in existing code, and tests
show significant performance improvements for some of the more complex examples.
Railroad diagrams may render differently, since they now no longer rely on
recursion using `Forward` expressions.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../{python3-pyparsing_3.3.2.bb => python3-pyparsing_3.3.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pyparsing_3.3.2.bb => python3-pyparsing_3.3.3.bb} (90%)
diff --git a/meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb b/meta/recipes-devtools/python/python3-pyparsing_3.3.3.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb
rename to meta/recipes-devtools/python/python3-pyparsing_3.3.3.bb
index 2565751f287..fbb0d642936 100644
--- a/meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb
+++ b/meta/recipes-devtools/python/python3-pyparsing_3.3.3.bb
@@ -10,7 +10,7 @@ BUGTRACKER = "https://github.com/pyparsing/pyparsing/issues"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=9c8a9625037eff2407f8456010875183"
-SRC_URI[sha256sum] = "c777f4d763f140633dcb6d8a3eda953bf7a214dc4eff598413c070bcdc117cbc"
+SRC_URI[sha256sum] = "928ae7e20211f3b6f3915a72f06a0cfd29ab9d24279dd6346b6b1a7146397d36"
inherit pypi python_flit_core
next prev parent reply other threads:[~2026-09-21 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 14:58 [PATCH 1/5] cairo: upgrade 1.18.4 -> 1.18.6 Richard Purdie
2026-09-21 14:58 ` [PATCH 2/5] harfbuzz: upgrade 14.4.0 -> 14.5.0 Richard Purdie
2026-09-21 14:58 ` Richard Purdie [this message]
2026-09-21 14:58 ` [PATCH 4/5] stress-ng: upgrade 0.22.00 -> 0.22.01 Richard Purdie
2026-09-21 14:58 ` [PATCH 5/5] utfcpp: upgrade 4.2.0 -> 4.2.1 Richard Purdie
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=20260921145835.1106731-3-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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