Use language: script for cudf-polars-ir-signatures pre-commit hook

[vyasr]

Description

The cudf-polars-ir-signatures pre-commit hook uses language: python but is just a local script (./ci/check_cudf_polars_ir.py) that only depends on stdlib modules (ast, argparse, sys, typing) and has a #!/usr/bin/env python3 shebang.

With language: python, pre-commit unnecessarily creates a virtualenv for this hook. language: script is the correct setting — it runs the entry point directly as an executable, relying on the shebang for interpreter selection, with no virtualenv overhead.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[jameslamb]

Sure, seems fine. By definition if precommit is runnable you must have a Python interpreter around, and this seems fine if you're not picky about which one.

[vyasr]

Sure, seems fine. By definition if precommit is runnable you must have a Python interpreter around, and this seems fine if you're not picky about which one.

The language key is used to determine the installation mechanism, more than the actual language of the hook, and the installation causes problems in some environments because for a local hook it will try to run pip install . and that can fail without the necessary requirements, e.g.

[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('/home/nfs/vyasr/.cache/pre-commit/repoh77sil0l/py_env-python3/bin/python', '-mpip', 'install', '.')
return code: 1
stdout: (none)
stderr:
    ERROR: Directory '.' is not installable. Neither 'setup.py' nor 'pyproject.toml' found.

I think whether or not it fails is probably dependent on pre-commit version and the behavior has changed. IOW lying about the language of the hook is the lesser of two evils since in some cases the status quo can fail outright.

[vyasr]

/merge