8000 Use our own version of unparse instead of `ruff_python_codegen` by coolreader18 · Pull Request #5633 · RustPython/RustPython · GitHub
[go: up one dir, main page]
Skip to content

Use our own version of unparse instead of ruff_python_codegen #5633

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

Jump to bottom
Merged
merged 3 commits into from
Mar 28, 2025
Merged

Use our own version of unparse instead of ruff_python_codegen #5633

merged 3 commits into from
Mar 28, 2025

Conversation

coolreader18
Copy link
Member
@coolreader18 coolreader18 commented Mar 28, 2025 •
edited
Loading

This further slims down rustpython-codegen's dependencies, and makes stringified __future__.annotations more accurate. We don't need all of ruff_python_codegen, since we only ever unparse expressions, not statements.

Uh oh!

There was an error while loading. Please reload this page.
@youknowone youknowone merged commit 58a17f3 into RustPython:main Mar 28, 2025
11 checks passed
@coolreader18 coolreader18 deleted the compiler-deps branch March 28, 2025 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@youknowone youknowone youknowone approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@coolreader18 @youknowone
0