Skip to content

Issues: psf/black

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
50 Open 68 Closed
50 Open 68 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Long lines that concatenate list comprehensions F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#4353 opened May 8, 2024 by tomkcook updated May 16, 2024
3
Trailing comma gives newline on wrong expressions F: linebreak How should we split up lines? F: trailing comma Full of magic T: bug Something isn't working
#3268 opened Sep 12, 2022 by jlubcke updated May 9, 2024
3
Strange formatting of fluent interface F: linebreak How should we split up lines? S: needs discussion Needs further hashing out before ready for implementation (on desirability, feasibility, etc.) T: style What do we want Blackened code to look like?
#571 opened Oct 17, 2018 by WouldYouKindly updated Mar 26, 2024
1
17
string_processing: Worse formatting of assert C: preview style Issues with the preview and unstable style. Add the name of the responsible feature in the title. F: linebreak How should we split up lines? F: strings Related to our handling of strings T: bug Something isn't working T: style What do we want Blackened code to look like?
#3210 opened Aug 5, 2022 by hauntsaninja updated Jan 30, 2024
string_processing: Handle overloaded operators when splitting long strings C: preview style Issues with the preview and unstable style. Add the name of the responsible feature in the title. F: linebreak How should we split up lines? F: strings Related to our handling of strings S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: enhancement New feature or request
#2334 opened Jun 13, 2021 by bbugyi200 updated Jan 30, 2024
4
Suboptimal line split choices with wrap_long_dict_values_in_parens C: preview style Issues with the preview and unstable style. Add the name of the responsible feature in the title. F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3452 opened Dec 19, 2022 by tolomea updated Dec 29, 2023
1
6
Wrapping lines of a function signature that uses the new python 3.12 generic type parameter syntax F: linebreak How should we split up lines? S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: style What do we want Blackened code to look like?
#4071 opened Nov 26, 2023 by Questionsdenombres updated Dec 3, 2023
1
Single line with binary operator in commented list causes additional line breaks F: linebreak How should we split up lines? T: bug Something isn't working
#4026 opened Nov 6, 2023 by zyzzyxdonta updated Nov 6, 2023
1
Undesired line breaks when using multiple assignments F: linebreak How should we split up lines? T: bug Something isn't working
#3854 opened Aug 24, 2023 by yilei updated Aug 24, 2023
Add linebreak in comprehension with complex element expression F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#2121 opened Apr 20, 2021 by Peilonrayz updated Jun 9, 2023
16
pylint inline comments wrapped to wrong line F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. F: linebreak How should we split up lines? T: bug Something isn't working
#2843 opened Jan 31, 2022 by drootang updated May 19, 2023
11
Addition of type ignore causes undesirable splitting on another line F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. F: linebreak How should we split up lines? T: bug Something isn't working
#3681 opened May 6, 2023 by hauntsaninja updated May 6, 2023
Less whitespace when a function call contains a single list/dict/tuple/string F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3621 opened Mar 23, 2023 by st-pasha updated Apr 24, 2023
5
line sometimes split in the middle of a dictionary .get() F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3579 opened Feb 22, 2023 by mccarthyp-snet updated Mar 30, 2023
Break expression in arguments if the call has comments. F: linebreak How should we split up lines?
#3626 opened Mar 28, 2023 by mvaled updated Mar 28, 2023
Black doesn't split too long for-in in list comprehension F: linebreak How should we split up lines? F: linetoolong Black makes our lines too long T: bug Something isn't working
#3498 opened Jan 15, 2023 by AdeliManesh updated Mar 10, 2023
2
Multiple accesses are turned multiline when the last argument of a call has a trailing comma F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3582 opened Feb 25, 2023 by halworsen updated Feb 26, 2023
2
Unnatural break due to overzealous omitting of optional parentheses F: linebreak How should we split up lines? F: parentheses Too many parentheses, not enough parentheses, and so on. T: bug Something isn't working
#236 opened May 20, 2018 by ambv updated Feb 10, 2023
4
Double list index results in newline F: linebreak How should we split up lines?
#3553 opened Feb 7, 2023 by davidgilbertson updated Feb 7, 2023
2
Long dict key with operators are oddly broken into multiple lines F: linebreak How should we split up lines? S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: style What do we want Blackened code to look like?
#3442 opened Dec 15, 2022 by yilei updated Feb 3, 2023
2
[style] Function default parameters - ugly lambda explosion F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3432 opened Dec 12, 2022 by Starwort updated Jan 29, 2023
1
Breaking # pyright: ignore[] used with # type: ignore[] comments on short lines F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3399 opened Nov 30, 2022 by Avasam updated Jan 19, 2023
3
Break long lines at dominant semantic features F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#3346 opened Oct 21, 2022 by naught101 updated Jan 13, 2023
5
Sensible minimum number of char width "won back" before indentation used. F: linebreak How should we split up lines? S: needs discussion Needs further hashing out before ready for implementation (on desirability, feasibility, etc.) T: style What do we want Blackened code to look like?
#2954 opened Mar 25, 2022 by mangelozzi updated Dec 23, 2022
9
Black doesn't wrap functions with parameter comments F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. F: linebreak How should we split up lines? T: bug Something isn't working
#3113 opened Jun 8, 2022 by liam-mipac updated Nov 18, 2022
ProTip! Mix and match filters to narrow down what you’re looking for.