From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
horms@kernel.org, sdf@fomichev.me, gal@nvidia.com,
jstancek@redhat.com, ast@fiberby.net
Subject: Re: [PATCH net-next 2/2] tools: ynl: pyynl: pull the --family resolution logic into the lib
Date: Tue, 30 Jun 2026 11:10:30 +0100 [thread overview]
Message-ID: <m2jyrgcp9l.fsf@gmail.com> (raw)
In-Reply-To: <20260630001432.2204298-3-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> When packaging YNL as a system level utility we added a --family
> argument which auto-resolves the full spec path from a well known
> path in /usr/share. Spelling out full YAML spec files is at this
> point only done in-tree, for example in the selftests which need
> the very latest YAML. But the selftests have their own wrapping
> classes for each family so test authors aren't really bothered
> by having to spell the paths out.
>
> Afford the same ease of use to the Python library users.
> Move the path resolution from the CLI code to the library.
> This simplifies the pyynl use by a lot:
>
> from pyynl import YnlFamily
>
> ynl = YnlFamily(family="netdev")
>
> Unless I'm missing a trick, resolving the /usr/share path
> is hard enough for most users to lean towards shelling out
> to ynl CLI with --output-json, which is sad.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> tools/net/ynl/pyynl/cli.py | 53 +++++------------------------
This breaks tools/net/ynl/tests/ethtool.py which currently imports from cli:
from cli import schema_dir, spec_dir
Otherwise, changes look good.
prev parent reply other threads:[~2026-06-30 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 0:14 [PATCH net-next 0/2] tools: ynl: pyynl: minor library ease of use improvements Jakub Kicinski
2026-06-30 0:14 ` [PATCH net-next 1/2] tools: ynl: pyynl: re-export the library API from the package root Jakub Kicinski
2026-06-30 7:28 ` Jan Stancek
2026-06-30 8:38 ` Donald Hunter
2026-06-30 0:14 ` [PATCH net-next 2/2] tools: ynl: pyynl: pull the --family resolution logic into the lib Jakub Kicinski
2026-06-30 10:10 ` Donald Hunter [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=m2jyrgcp9l.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.