From: Leon Anavi <leon.anavi@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Leon Anavi <leon.anavi@konsulko.com>
Subject: [meta-python][PATCH 3/3] python3-invoke: Upgrade 2.2.1 -> 3.0.3
Date: Mon, 20 Jul 2026 17:34:26 +0300 [thread overview]
Message-ID: <20260720143426.809643-3-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20260720143426.809643-1-leon.anavi@konsulko.com>
Upgrade to release 3.0.3:
- Reverted the @task return value type hint change; it actually
just makes things worse. Taking this one back to the drawing
table for later.
From 3.0.2:
- Define a custom __repr__ for Promise so it can be displayed in
interactive sessions or other debug contexts, without running
afoul of AttributeError. Thanks to Leonid Shvechikov for the
original bug report.
- Make the return value type hint for @task more specific; as-is it
would trigger typecheck errors when handing regular, decorated
task functions as inputs to add_task and similar methods.
From 3.0.1:
- Minor tweaks to documentation and type hints/inheritance (mostly
around Promise).
From 3.0.0:
- Add access to the core CLI parser's remainder value, via
Context.remainder - this allows for more elegant wrapper tasks.
- Update the return value, and type hint, of run and friends to be
Result instead of Optional[Result].
- run now includes local subprocess PIDs in Result objects (as
.pid), via the new Runner.get_pid method. This may be generally
useful for auditing or similar tasks, but is primarily intended
for users of disown=True who want to perform their own subprocess
management.
- Fix a grab bag's worth of Sphinx doc render problems, among which
were some class attributes (eg Context.command_cwds) that had
silently disappeared from the class' autodoc output after our
2.0 release.
- Expanded mypy type hint checking to more of the codebase &
generally touched up some type hints here and there. More of
this is planned to occur as we go.
- Dropped support for Python versions <3.9. That's right, we've
caught up to Python's own EOL regime... as of late 2024! As part
of this change, we also switched over to using pyproject.toml for
packaging metadata.
Fixes:
WARNING: python3-invoke-3.0.3-r0 do_check_backend: QA Issue:
inherits setuptools3 but has pyproject.toml with setuptools.build_meta,
use the correct class [pep517-backend]
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
.../{python3-invoke_2.2.1.bb => python3-invoke_3.0.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-python/recipes-devtools/python/{python3-invoke_2.2.1.bb => python3-invoke_3.0.3.bb} (74%)
diff --git a/meta-python/recipes-devtools/python/python3-invoke_2.2.1.bb b/meta-python/recipes-devtools/python/python3-invoke_3.0.3.bb
similarity index 74%
rename from meta-python/recipes-devtools/python/python3-invoke_2.2.1.bb
rename to meta-python/recipes-devtools/python/python3-invoke_3.0.3.bb
index bcff343480..e9d19da088 100644
--- a/meta-python/recipes-devtools/python/python3-invoke_2.2.1.bb
+++ b/meta-python/recipes-devtools/python/python3-invoke_3.0.3.bb
@@ -3,9 +3,9 @@ HOMEPAGE = "https://www.pyinvoke.org/"
LICENSE = "BSD-2-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=a8815068973f31b78c328dc067e297ab"
-SRC_URI[sha256sum] = "515bf49b4a48932b79b024590348da22f39c4942dff991ad1fb8b8baea1be707"
+SRC_URI[sha256sum] = "437b6a622223824380bfb4e64f612711a6b648c795f565efc8625af66fb57f0c"
-inherit pypi setuptools3
+inherit pypi python_setuptools_build_meta
RDEPENDS:${PN} += " \
python3-fcntl \
--
2.47.3
prev parent reply other threads:[~2026-07-20 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:34 [meta-python][PATCH 1/3] python3-imageio: Upgrade 2.37.3 -> 2.37.4 Leon Anavi
2026-07-20 14:34 ` [meta-python][PATCH 2/3] python3-autobahn: Upgrade 26.6.1 -> 26.7.1 Leon Anavi
2026-07-20 14:34 ` Leon Anavi [this message]
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=20260720143426.809643-3-leon.anavi@konsulko.com \
--to=leon.anavi@konsulko.com \
--cc=openembedded-devel@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