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.

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

Pyupgrade as a code modification backend #752

Open
akaihola opened this issue Oct 6, 2024 · 0 comments · May be fixed by #755
Open

Pyupgrade as a code modification backend #752

akaihola opened this issue Oct 6, 2024 · 0 comments · May be fixed by #755
Assignees
Labels
enhancement New feature or request

Comments

@akaihola
Copy link
Owner

akaihola commented Oct 6, 2024

Similar to flynt and isort, pyupgrade could be supported as a backend tool for making modifications to Python code.

pyupgrade describes itself as:

A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.

A previous effort to make Darker support pyupgrade was started already in August 2020 by @Carreau in #51. Two years later, support for flynt was being developed (PR #308), and the thought was that the exact same mechanics of running the backend could be applied to pyupgrade.

All the relevant discussion is still available in the closed issue #51, and the original branch has been copied from @Carreau's fork into the main Darker repository as tree/pyupgrade

@akaihola akaihola added the enhancement New feature or request label Oct 6, 2024
@akaihola akaihola self-assigned this Oct 6, 2024
@akaihola akaihola moved this from Done to Todo in Darker and Graylint development Oct 6, 2024
@akaihola akaihola linked a pull request Oct 19, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant