-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Long string remains unchanged #1787
Comments
Thanks @hugovk, it worked. Should I create a PR on the documentation to add this option? |
Good to hear! Nope, it's intentionally undocumented until the related crashes are fixed, and then it'll become the default when it's more stable. But thanks for the offer! |
Just to be clear, if we can't get the extra string processing stable enough it won't ever be released. On the flip side, that's unlikely as there already has been efforts by bbugyi200! Closing as there isn't anything actionable in this issue. |
It doesn't work on the string |
@asgmeonerandom the string is left unchanged because there isn't anything for Black to split on (i.e. no spaces).
|
mine has spaces between variables |
Is there any way of setting this setting in the [tool.black]
experimental_string_processing = true
experimental-string-processing = true
experimental_string_processing = "true"
experimental-string-processing = "true" but none worked. Thanks |
@lyz-code, the |
Long strings remain unchanged.
To Reproduce Steps to reproduce the behavior:
Expected behavior: Formatting should meet the behaviour of #1132 .
Environment (please complete the following information):
pip install git+git://github.com/psf/black
)Does this bug also happen on master? Yes, tested with black.now.sh
Additional context: After reviewing the git log, I've seen that the #1132 PR was merged into the branch
origin/poetry
but not into the current master. Although the code seems to be presentThe text was updated successfully, but these errors were encountered: