From: Luca Vizzarro <luca.vizzarro@arm.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Luca Vizzarro <luca.vizzarro@arm.com>,
Patrick Robb <probb@iol.unh.edu>,
Paul Szczepanek <paul.szczepanek@arm.com>
Subject: [PATCH 0/3] dts: fix doc issues
Date: Fri, 31 Jan 2025 19:19:21 +0000 [thread overview]
Message-ID: <20250131191924.1936157-1-luca.vizzarro@arm.com> (raw)
Hi everyone,
The first patch will finally get rid of any warnings in the doc build.
Whereas the other two patches are required to build docs or even run DTS
in Python 3.12 and 3.13.
Python 3.13 has introduced a new breaking change without warning, which
broke the way we used a specific stdlib function.
Finally, we were relying on an older version of our SSH client library
fabric which backwards-compatibility was dropped in Python 3.12, raising
further problems while building docs.
Best,
Luca
Luca Vizzarro (3):
dts: remove use of field validators
dts: stop using partial in enums
dts: bump up fabric version
doc/guides/conf.py | 9 +-
dts/framework/config/__init__.py | 18 +-
dts/framework/remote_session/__init__.py | 2 +-
.../interactive_remote_session.py | 2 +-
.../remote_session/remote_session.py | 2 +-
dts/framework/remote_session/testpmd_shell.py | 145 +++++++--------
dts/framework/testbed_model/capability.py | 6 +-
dts/poetry.lock | 165 ++++++++++++++----
dts/pyproject.toml | 2 +-
9 files changed, 219 insertions(+), 132 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-31 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:19 Luca Vizzarro [this message]
2025-01-31 19:19 ` [PATCH 1/3] dts: remove use of field validators Luca Vizzarro
2025-01-31 19:19 ` [PATCH 2/3] dts: stop using partial in enums Luca Vizzarro
2025-01-31 19:19 ` [PATCH 3/3] dts: bump up fabric version Luca Vizzarro
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=20250131191924.1936157-1-luca.vizzarro@arm.com \
--to=luca.vizzarro@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).