Skip to content

Upgrade out of date Black to a version supporting Python 3.9 to avoid it erroring out #681

@CAM-Gerlach

Description

@CAM-Gerlach

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently, our code supports Python 3.7-3.9, the last of which has been out for almost a year now. Accordingly, I specify target versions from 3.7 through 3.9 in my Black config, i.e. target-version = ["py37", "py38", "py39"]. However, given the Black release, 20.8, is over a year old and is the last to not support Python 3.9 released a couple months later, Black errors out on every file due to not recognizing the target-version key, and thus rendering it unusable for me through Mega-Linter.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Upgrade Black to a version >=21.4 that supports Python 3.9; preferably the latest version that fixes issues with the soon to be default experimental-string-processing that many projects are using in production now, as well as other issues.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Don't upgrade Black; which will block support for language versions newer than Python 3.8, as well as not take advantage of the latest features and bug fixes.

Additional context
Add any other context or screenshots about the feature request here.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions