This message was deleted.
# contribute
s
This message was deleted.
t
Maybe `black`changed and no longer accepts stage "pre-commit" ?
r
gives the same error
s
I just do:
Copy code
pip install pre-commit
pre-commit install
pre-commit run --all-files
did you run
pre-commit install
?
r
no I didnt because I dont think it is necessary.
did it now but makes no difference
It is either python 3.9.6 which I’m running because I want to use spark or I’ve messed up something else that is interfering with pre-commit
e
So yeah you don’t have to use the same venv to run the code as you do to commit it but it’s annoying nonetheless
Quite possible that some strange dependency set pushed you onto an old version of something
r
that is actually a possible workaround that I can try indeed
e
Worth a try — I thought pyspark worked with newer python versions (our tests run them), but it might be something bespoke to your/a more general case, or I could be wrong in some way
s
I’m running
Python 3.9.13
and it’s fine for me
the
.pre-commit-config.yaml
defines the versions of things
r
Ok so its working on 3.11.4. Thanks @Stefan Krawczyk let me try 3.9.13 too
😅 1
👍 1
e
Heh would be very funny if it were a patch version of python that had a pre-commit backwards incompatibility. My guess is its dependency resolution that does it, bringing in an old pre-commit or black version
As in, the python version isn’t the piece that makes it break, it just alters the dep resolution in a way that makes it break
r
Thanks for the help all, have a great Christmas! 🎄
🎅 1
🙌 1
e
Yeah thanks for the contributions. Merry Christmas!