-
Notifications
You must be signed in to change notification settings - Fork 0
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
Formatter fails to run #16
Comments
Hi & thanks! Removed that => can u verify and close, if so? |
It seems that the newest version does run.
The new version changes all the double-quote block strings ( |
Can you detail what you mean here (example), triple quoted strings are still formatted to /tmp ❯ black --version
black, version 20220330
/tmp ❯ cat r.py
'''
mod doc
'''
def foo():
'''func doc'''
foo = "bar"; baz= [ "bar"]
/tmp ❯ cat r.py| black -
"""
mod doc
"""
def foo():
"""func doc"""
foo = 'bar'
baz = ['bar']
reformatted -
All done! ✨ 🍰 ✨
1 file reformatted. |
Previous behaviour we used:
With a newer version of axblack
The |
Ok, I see what you mean: The version of 2020 january 30 could not format on stdin (
Means: ALL triple quoted strings, docstrings or not, where turned to double apos. While our documented style, since quite a while is: Double quotes ONLY for docstrings. Code only single quotes, triple quoted or not. I think the change followed a change the PSF/black version did also back then, once. I cannot change it back to the old behaviour now (do find the current form also better but that is a matter of personal taste). I would say, if you really want to keep double apo tripple quotes within your codebases, then nail the black version to 20200130 - which means, you have to nail the click version as well. Sorry for that. |
closing - reopen or send a PR for the cli flag. |
Describe the bug
A freshly installed axblack (
pip install axblack==20220321
) fails to run with an error patching_unicodefun
fromclick
. It seems between release8.0.4
and8.1.0
of click, that method was removed.To Reproduce
click
)black
on any projectExpected behavior
Code to be formatted.
Environment (please complete the following information):
Does this bug also happen on master? To answer this, you have two options:
Did not test this on master.
Additional context
Changing my formatter install command to the following resolves the issue:
The text was updated successfully, but these errors were encountered: