Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [pre-commit] Stop using deprecated language script
Date: Tue, 16 Jun 2026 09:46:45 -0400	[thread overview]
Message-ID: <d7284986-1776-41cc-80bf-b5bf068530de@simark.ca> (raw)
In-Reply-To: <20260616092346.3242305-1-tdevries@suse.de>

On 6/16/26 5:23 AM, Tom de Vries wrote:
> In v4.4.0, pre-commit renamed language script to unsupported_script.
> 
> The rename was done to stress that pre-commit doesn't provide an environment
> for the script to run in [1].
> 
> The language script is now a deprecated alias for unsupported_script, and the
> plan seems to be to initially produce a deprecation warning, and eventually
> remove support for the alias completely.
> 
> Start using the new name: unsupported_script.
> 
> Furthermore, the check-include-guards hook uses language python, and indeed it
> uses a python script, but it doesn't really need a virtual environment.  It
> imports modules fnmatch, re, sys and typing, all of which are available in
> python 3.10 and later, which is the environment pre-commit itself requires
> (because we require pre-commit v4.5.1 or later, and pre-commit requires python
> 3.10 since v4.4.0).  So while we're at it, use unsupported_script for this
> hook as well, reducing the amount of environments pre-commit has to manage.
> 
> Tested using "pre-commit run --all-files" with python 3.10, as well as 3.13.
> 
> [1] https://github.com/pre-commit/pre-commit/pull/3577

From reading the pre-commit doc, I didn't understand the difference
between "unsupported_script" and "unsupported", did you?

Simon

  reply	other threads:[~2026-06-16 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  9:23 Tom de Vries
2026-06-16 13:46 ` Simon Marchi [this message]
2026-06-16 15:32   ` Tom de Vries
2026-06-16 15:46     ` Simon Marchi

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=d7284986-1776-41cc-80bf-b5bf068530de@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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