Łukasz Langa
Łukasz Langa
This missed the boat for inclusion in Python 3.9 which accepts security fixes only as of today.
Reverting the PR would be a good start but I'd love some configurability here. [I do also have a horse in this race](https://github.com/ambv/black/).
I'll submit a PR soon :-)
The difference is this `\u3000` aka `\n{IDEOGRAPHIC SPACE}` character that was somehow removed by Black:
The reason I'm hesitant to merge this is that this introduces a weird dependency between runs in Black: - Black leaves existing parentheses; - but sometimes it puts parentheses by...
Thanks for your report! I agree Black should do better here but bear in mind that your doctests are very brittle as is. If you tell your text editor (or...
Raw Python C API is not a silver bullet. We'd have to rewrite parts of the program in straight C and since most of it operates on blib2to3.pytree, we'd need...
It would be amazing to compile Black with @mypyc/mypyc. If I understand correctly, @msullivan is interested in making it happen. FTR, if this will require changes to the Black codebase,...
Workaround until I figure out what to do here: wrap the string in parentheses. Then you don't even have to explicitly concatenate it with `+`.
We will put optional parentheses in this situation.