Skip to content
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

Elaborate on Python support policy #2819

Merged
merged 4 commits into from
Jan 28, 2022
Merged

Elaborate on Python support policy #2819

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e0271c8
Elaborate on Python support policy (#2251)
felix-hilden Jan 28, 2022
94c7e81
Add changelog entry
felix-hilden Jan 28, 2022
0e69a3d
Explicit is better than implicit
felix-hilden Jan 28, 2022
534e02b
Add upper version bounds
felix-hilden Jan 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,7 @@ and the first release covered by our new stability policy.
- Change HTML theme to Furo primarily for its responsive design and mobile support
(#2793)
- Deprecate the `black-primer` tool (#2809)
- Document Python support policy (#2819)
Copy link
Collaborator

@ichard26 ichard26 Jan 28, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arguably this could count as a highlight, but I'd prefer input from other maintainers.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hesitated, because it doesn't really affect anything currently 😄 but I can change it if you'd like

Copy link
Collaborator

@cooperlees cooperlees Jan 28, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't hurt to have it in the hi-lights or here ... Hilights might make more people come read it advertising it there ...

Should we link to the paragraph?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if I misunderstood you Cooper, but I think Richard was asking if it should be put in the "highlights" section at the very top instead


## 21.12b0

Expand Down
11 changes: 9 additions & 2 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,16 @@ readability because operators are misaligned. Disable W503 and enable the
disabled-by-default counterpart W504. E203 should be disabled while changes are still
[discussed](https://github.com/PyCQA/pycodestyle/issues/373).

## Does Black support Python 2?
## Which Python versions does Black support?

Support for formatting Python 2 code was removed in version 22.0.
Currently the runtime requires Python 3.6-3.10. Formatting is supported for files
containing syntax from Python 3.3 to 3.10. We promise to support at least all Python
versions that have not reached their end of life. This is the case for both running
_Black_ and formatting code.

Support for formatting Python 2 code was removed in version 22.0. While we've made no
plans to stop supporting older Python 3 minor versions immediately, their support might
also be removed some time in the future without a deprecation period.

## Why does my linter or typechecker complain after I format my code?

Expand Down