-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest version of Black (22.12.0) breaks Darker #412
Comments
also ran into it, see #403 is there any timeline for a new darker version or an obvious way to pin the black version in the darker action? |
yeah it'd be great if darker allows customization of the version of black used. I don't see it under the configuration options. |
I add |
how do I downgrade the version of black that darker uses in my git pre-commit hook? My repos:
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v2.3.0
hooks:
- id: check-yaml
- id: end-of-file-fixer
- id: trailing-whitespace
- repo: https://github.com/akaihola/darker
rev: 1.5.1
hooks:
- id: darker
args:
- --line-length=120
language_version: python3 and I have |
@victorcui96, I think each pre-commit hook installs into its own environment so modifying your project's requirements.txt will have no effect. The above referencing issue has a fix though, so applying that in your pre commit config would look like:
|
@leej3 thanks for that! I didn't know each pre-commit hook installs in its own environment. I changed to
and it worked. |
This has been fixed in Darker 1.6.0. |
22.12.0 (exception occurs):
22.8.0 (works fine):
The text was updated successfully, but these errors were encountered: