DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Luca Vizzarro <Luca.Vizzarro@arm.com>
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>,
	 Paul Szczepanek <paul.szczepanek@arm.com>
Subject: Re: [PATCH 1/2] dts: update mypy static checker
Date: Wed, 29 May 2024 13:22:58 +0200	[thread overview]
Message-ID: <CAOb5WZY3QzM75mk+yYwz3jTD-1jtPuZ6ymyehn4xy8jxqbOMYw@mail.gmail.com> (raw)
In-Reply-To: <455e78ea-ad27-467e-ab3b-cfacb9de970e@arm.com>

On Tue, May 14, 2024 at 1:30 PM Luca Vizzarro <Luca.Vizzarro@arm.com> wrote:
>
> On 13/05/2024 17:02, Juraj Linkeš wrote:
> >>       def _filter_test_cases(
> >>           self, test_suite_class: type[TestSuite], test_cases_to_run: Sequence[str]
> >> -    ) -> tuple[list[MethodType], list[MethodType]]:
> >> +    ) -> tuple[list[FunctionType], list[FunctionType]]:
> >
> > Does changing inspect.getmembers(test_suite_class, inspect.isfunction)
> > to use inspect.ismethod not work?
>
> Nope, for some reason when running inspect.ismethod on the TestSuite
> class methods it returns False... I didn't investigate further, as just
> isfunction works and it's not a deal breaker.

I looked a bit into this and ismethod() returns True for instance
methods (the function knows the instance it's bound to) and we're
working with class members (in this case, there's no instance
associated with the function, so it actually can't be a method), so we
have to use isfunction() and as such the change to FunctionType is the
proper one.

  reply	other threads:[~2024-05-29 11:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 10:57 [PATCH 0/2] dts: update mypy and clean up Luca Vizzarro
2024-05-09 10:57 ` [PATCH 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-13 16:02   ` Juraj Linkeš
2024-05-14 11:30     ` Luca Vizzarro
2024-05-29 11:22       ` Juraj Linkeš [this message]
2024-05-09 10:57 ` [PATCH 2/2] dts: clean up config types Luca Vizzarro
2024-05-13 16:12   ` Juraj Linkeš
2024-05-14 11:30     ` Luca Vizzarro
2024-05-29 11:41   ` Juraj Linkeš
2024-05-14 11:34 ` [PATCH v2 0/2] dts: update mypy and clean up Luca Vizzarro
2024-05-14 11:34   ` [PATCH v2 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-24 14:51     ` Patrick Robb
2024-05-28 12:00       ` Luca Vizzarro
2024-05-29 10:58         ` Juraj Linkeš
2024-05-29 11:39     ` Juraj Linkeš
2024-05-29 15:20       ` Luca Vizzarro
2024-05-14 11:34   ` [PATCH v2 2/2] dts: clean up config types Luca Vizzarro
2024-05-24 16:13     ` Patrick Robb
2024-05-20 15:37   ` [PATCH v2 0/2] dts: update mypy and clean up Nicholas Pratte
2024-05-21 14:59     ` Luca Vizzarro
2024-05-24 13:47       ` Nicholas Pratte
2024-05-24 16:17   ` Patrick Robb
2024-05-28 12:05     ` Luca Vizzarro
2024-05-29 10:44       ` Juraj Linkeš
2024-05-30 15:19 ` [PATCH v3 " Luca Vizzarro
2024-05-30 15:19   ` [PATCH v3 1/2] dts: update mypy static checker Luca Vizzarro
2024-05-30 20:23     ` Jeremy Spewock
2024-05-31  9:29     ` Juraj Linkeš
2024-06-17 15:28     ` Nicholas Pratte
2024-05-30 15:19   ` [PATCH v3 2/2] dts: clean up config types Luca Vizzarro
2024-05-30 20:23     ` Jeremy Spewock
2024-05-31  9:29     ` Juraj Linkeš
2024-06-17 15:30     ` Nicholas Pratte
2024-06-19 23:02   ` [PATCH v3 0/2] dts: update mypy and clean up Thomas Monjalon

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=CAOb5WZY3QzM75mk+yYwz3jTD-1jtPuZ6ymyehn4xy8jxqbOMYw@mail.gmail.com \
    --to=juraj.linkes@pantheon.tech \
    --cc=Luca.Vizzarro@arm.com \
    --cc=dev@dpdk.org \
    --cc=jspewock@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    /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).