But codespell doesn't invoke pre-commit on deleted files, does it?

And codespell doesn't fail in this case:

$ codespell /non/existent/file
$ 

Could you perhaps investigate further and reproduce the issue outside of pre-commit?

EDIT: Got it, sorry about the misunderstanding:

$ codespell --exclude-file /non/existent/file
Traceback (most recent call last):
  File "/home/dp165978/.local/bin/codespell", line 8, in <module>
    sys.exit(_script_main())
             ^^^^^^^^^^^^^^
  File "/volatile/src/codespell/codespell_lib/_codespell.py", line 1102, in _script_main
    return main(*sys.argv[1:])
           ^^^^^^^^^^^^^^^^^^^
  File "/volatile/src/codespell/codespell_lib/_codespell.py", line 1261, in main
    build_exclude_hashes(exclude_file, exclude_lines)
  File "/volatile/src/codespell/codespell_lib/_codespell.py", line 726, in build_exclude_hashes
    with open(filename, encoding="utf-8") as f:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/non/existent/file'
$ 

We could catch the FileNotFoundError and emit an error message. However, I believe codespell should still exit when passing a config file that does not exist as an argument. That's what other commands do:

$ ruff --config /non/existent/file
error: invalid value '/non/existent/file' for '--config <CONFIG_OPTION>'

  tip: A `--config` flag must either be a path to a `.toml` configuration file
       or a TOML `<KEY> = <VALUE>` pair overriding a specific configuration
       option

It looks like you were trying to pass a path to a configuration file.
The path `/non/existent/file` does not point to a configuration file

For more information, try '--help'.
$ 
$ grep --file=/non/existent/file 
grep: /non/existent/file: No such file or directory
$ 

Thanks for the quick reply!

But codespell doesn't invoke pre-commit on deleted files, does it?

No, it does not.

We could catch the FileNotFoundError and emit an error message. However, I believe codespell should still exit when passing a config file that does not exist as an argument.

I think there's a misunderstanding: I totally do agree that exiting with an error is fine if the config file is missing. However, here we have a valid config but only one of the specified files within the config does not exist. I'd argue that this is not necessarily a reason to exit with a non-zero exit code - though of course it's up to you to decide ;)

The following for example exits without an error:

$ ruff check --exclude /this/does/not/exist

@luzpaz Looks similar but unrelated to me: the pyproject.toml file appears to be corrupted and tomllib raises an exception — which codespell doesn't catch.

EDIT: I would create a new issue for that. What's your opinion? Should codespell exit, or just emit a warning and keep going?

What's your opinion? Should codespell exit, or just emit a warning and keep going?

Not sure what the implications for ignoring the warning would be...