Just occurred to me when I wanted to update nbqa-ruff to v0.4.6 (need to keep this in sync with ruff manually, please change): How does pixi play with pre-commit? Would I still have a conda base env / the system Python to base pre-commit on? Sounds like trouble for some things...

I just confirmed that: pixi run pre-commit leads to An unexpected error has occurred: CalledProcessError: command: ('/mnt/econ/lcm/lcm/.pixi/envs/default/bin/python3.12', '-mvirtualpenv', '/home/hmg/.cache/pre-commit/repor0qq6lyq/py_env-python3.11', '-p', 'python3.11') because the tool.ruff section still specifies target-version = "py311" 😆

Can we somehow use the pixi-installed Python automatically when pre-commit is run?

1. Since this has happened before, and I know my forgetful brain, I've added a custom pre-commit hook that checks whether these versions are out-of-date.
2. Yes, this can definitely lead to problems. In principle, you can enter a pixi shell, which is similar to activating a conda environment. I don't know whether the pre-commit hooks use the correct Python version in this case though

Actually, I think we do not want that. I think this would also be difficult with the pre-commit CI, since there we would require the pixi environment as well.

I think the version now should work as before under conda.

But it worked under conda only if you activated the correct environment or your activated Python happened to be the correct version, right?

Okay, so there may be more clever solutions that I'm not aware of, but I think the easiest for now is to use pixi like conda.

I.e., you activate the pixi environment before you work in a project.

Alternatively, you could start with pixi run pre-commit install, and then afterwards run pixi run git commit -m "commit msg", which would use the correct Python version.