linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: "John B. Wyatt IV" <jwyatt@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
	linux-rt-users@vger.kernel.org,
	 kernel-rts-sst <kernel-rts-sst@redhat.com>,
	 "John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: Re: [PATCH] tuna: Add Pyright helper
Date: Fri, 25 Jul 2025 13:54:55 -0400 (EDT)	[thread overview]
Message-ID: <d797a0e1-b5a5-9cb1-1d66-5d69cc99658c@redhat.com> (raw)
In-Reply-To: <20250722213710.14464-1-jwyatt@redhat.com>



On Tue, 22 Jul 2025, John B. Wyatt IV wrote:

> Pyright is a common tool to assist with linting and finding errors in
> Python programs with an LSP like Visual Studio Code, Neovim, and Emacs. _("")
> syntax convention is used by gettext for translations and is a common default
> but Pyright needs to be set to not give an error for it. Add 
__builtins__.pyi
> with the _() convention to satisfy Pyright.
> 
> Signed-off-by: John B. Wyatt IV <jwyatt@redhat.com>
> Signed-off-by: John B. Wyatt IV <sageofredondo@gmail.com>
> ---
>  __builtins__.pyi | 1 +
>  1 file changed, 1 insertion(+)
>  create mode 100644 __builtins__.pyi
> 
> diff --git a/__builtins__.pyi b/__builtins__.pyi
> new file mode 100644
> index 0000000..0e3a4b2
> --- /dev/null
> +++ b/__builtins__.pyi
> @@ -0,0 +1 @@
> +def _(s: str) -> str: ...
> -- 
> 2.50.1
> 
> 
> 
Signed-off-by: John Kacur <jkacur@redhat.com>


      reply	other threads:[~2025-07-25 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 21:37 [PATCH] tuna: Add Pyright helper John B. Wyatt IV
2025-07-25 17:54 ` John Kacur [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=d797a0e1-b5a5-9cb1-1d66-5d69cc99658c@redhat.com \
    --to=jkacur@redhat.com \
    --cc=jwyatt@redhat.com \
    --cc=kernel-rts-sst@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sageofredondo@gmail.com \
    --cc=williams@redhat.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).