[pre-commit.ci] pre-commit autoupdate
updates:
@carlio, how do you feel about removing python 3.6 support ?
I think I had planned to do this as part of a 1.8 release but then I got distracted and haven't looked at prospector for a while. (There are RC builds on PyPI but need to remember where I got to before I do a real release)
Do you want to do a last release for python 3.6 or could I remove it now ?
Just leave it as is for now because I need to go back and remember where I got do with things, I don't want to make a bugfix release removing 3.6 compatibility and I can't remember if the 1.8 branch (develop) is ready for a full release yet.
@carlio we have a deadlock here, to fix pre-commit we need to fix poetry and prospector itself, but to fix poetry we need to fix pre-commit. I'm going to fix poetry and merge with pre-commit failing then fix prospector and merge with pre-commit failing, then fix pre-commit.
This fix prospector and seemingly pre-commit but will fail as soon as this branch is merged and the temporary commit disappear.