On Fri, Sep 27, 2024 at 8:57 PM Vincent Fazio <vfazio@xxxxxxxxxxx> wrote: > > This resolves a strict no-untyped-call mypy warning. > > Signed-off-by: Vincent Fazio <vfazio@xxxxxxxxxxx> > --- Ok, so I see this is how it's done in the standard library but why? If an error doesn't take arguments, one should raise its type? Could you elaborate more in the commit message? Bart
Re: [libgpiod][PATCH 12/22] bindings: python: raise exception type, not exception instance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [libgpiod][PATCH 12/22] bindings: python: raise exception type, not exception instance
- From: Bartosz Golaszewski <brgl@xxxxxxxx>
- Date: Tue, 8 Oct 2024 15:23:25 +0200
- In-reply-to: <20240927-vfazio-mypy-v1-12-91a7c2e20884@xes-inc.com>
- References: <20240927-vfazio-mypy-v1-0-91a7c2e20884@xes-inc.com> <20240927-vfazio-mypy-v1-12-91a7c2e20884@xes-inc.com>
- References:
- Prev by Date: Re: [libgpiod][PATCH 13/22] bindings: python: selectively use f-strings
- Next by Date: Re: [libgpiod][PATCH 14/22] bindings: python: tests: fix duplicate test name
- Previous by thread: [libgpiod][PATCH 12/22] bindings: python: raise exception type, not exception instance
- Next by thread: [libgpiod][PATCH 09/22] bindings: python: fix LineRequest union-attr type errors
- Index(es):
 |