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
354 Open 2,268 Closed
354 Open 2,268 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

Enable --experimental-string-processing to be default 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 T: style What do we want Blackened code to look like?
#2188 opened May 3, 2021 by cooperlees
@cooperlees
37 🎉 7
Improving the contributing experience C: maintenance Related to project maintenance, e.g. CI, testing, policy changes, releases help wanted Extra attention is needed T: documentation Improvements to the docs (e.g. new topic, correction, etc)
#2238 opened May 17, 2021 by ichard26
@ichard26
23 🎉 4
Use optional parentheses more often F: parentheses Too many parentheses, not enough parentheses, and so on. F: symmetry Fixing this would require Black to understand symmetry. T: style What do we want Blackened code to look like?
#2156 opened Apr 27, 2021 by cdce8p
2
33 🎉 1
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
1
17 🎉 1
List concatenation, multiple lines F: linebreak How should we split up lines? F: symmetry Fixing this would require Black to understand symmetry. help wanted Extra attention is needed T: enhancement New feature or request T: style What do we want Blackened code to look like?
#260 opened May 26, 2018 by sebdiem
2
Assert statement condition broken up in unfortunate way F: parentheses Too many parentheses, not enough parentheses, and so on. F: symmetry Fixing this would require Black to understand symmetry. T: style What do we want Blackened code to look like?
#348 opened Jun 14, 2018 by madig
8
Cython grammar support C: parser How we parse code. Or fail to parse it. help wanted Extra attention is needed S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: enhancement New feature or request
#359 opened Jun 15, 2018 by ambv
19
Reflows of inline comments can cause misalignment F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. T: enhancement New feature or request
#379 opened Jun 26, 2018 by quodlibetor
17
Provide lists of lint / pycodestyle rules that Black makes obsolete T: documentation Improvements to the docs (e.g. new topic, correction, etc)
#429 opened Jul 31, 2018 by nixjdm
11
no opinion on tuple assignment parentheses? F: parentheses Too many parentheses, not enough parentheses, and so on. T: enhancement New feature or request
#445 opened Aug 13, 2018 by matejcik
7
Comments interfering with fluent formatting F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. T: bug Something isn't working
#458 opened Aug 17, 2018 by max-sixty
3
No configuration used for paths after the first T: bug Something isn't working
#4461 opened Sep 18, 2024 by tmct
Line too long: Attribute chain F: linetoolong Black makes our lines too long T: style What do we want Blackened code to look like?
#510 opened Sep 13, 2018 by decibyte
5
Consider where "point/cursor" should end up C: integrations Editor plugins and other integrations
#516 opened Sep 17, 2018 by kootenpv
6
[RFE] Support gitignore-like include/exclude patterns C: configuration CLI and configuration
#541 opened Sep 29, 2018 by behnam
3
not (x in y) -> x not in y; not (x is y) -> x is not y T: enhancement New feature or request T: style What do we want Blackened code to look like?
#212 opened May 16, 2018 by JelleZijlstra
6
Redundant parentheses around lists F: parentheses Too many parentheses, not enough parentheses, and so on. 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?
#608 opened Nov 14, 2018 by cypreess
7
Bug: linebreak in comparison in parens with comments in conditional is not stable C: invalid code Black destroyed a valid Python file F: comments The syntactic kind. Not in the language grammar, always on our minds. Best bugs. T: bug Something isn't working
#638 opened Dec 12, 2018 by Zac-HD
4
blackd toml section C: configuration CLI and configuration S: accepted The changes in this design / enhancement issue have been accepted and can be implemented T: enhancement New feature or request
#667 opened Jan 10, 2019 by ptdel
4
Is --target-version the minimum or should all be explicitly listed? C: configuration CLI and configuration T: documentation Improvements to the docs (e.g. new topic, correction, etc)
#751 opened Mar 14, 2019 by hugovk
16
Black's public API C: api One day Black will have an API ... T: enhancement New feature or request
#779 opened Mar 23, 2019 by paugier
20
Black should chop down long call chains which are not in an assignment F: linebreak How should we split up lines? T: style What do we want Blackened code to look like?
#792 opened Apr 1, 2019 by ghost
1
Line too long: Lambda with many parameters F: linetoolong Black makes our lines too long T: style What do we want Blackened code to look like?
#809 opened Apr 18, 2019 by mikelane
13
Support inline per-file target version C: configuration CLI and configuration T: enhancement New feature or request
#811 opened Apr 20, 2019 by scop
3
Black doesn't format expressions inside f-strings C: parser How we parse code. Or fail to parse it. F: strings Related to our handling of strings T: enhancement New feature or request T: style What do we want Blackened code to look like?
#567 opened Oct 16, 2018 by mxr
13
ProTip! Exclude everything labeled bug with -label:bug.