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

RUFFs RET504 rule (unnecessary assignment before return statement) #6305

Closed
wants to merge 1 commit into from

Conversation

bigcat88
Copy link
Contributor

@bigcat88 bigcat88 commented Jan 1, 2025

Ruff docs regarding this rule.

ruff check . --unsafe-fixes --fix was performed and then everything was checked to see if it was replaced correctly.

If this rule is not needed, please just close the PR (since it affects all files, it will need to be constantly rebased, if not merged, which is lazy).

@comfyanonymous
Copy link
Owner

I'm not against these types of format rules but they should be introduced gradually not all at once.

@bigcat88
Copy link
Contributor Author

bigcat88 commented Jan 2, 2025

If you suggest making a separate PR for each file/pair of files, wouldn't that be spammy in the commit/changelog?

If it's only for one RUFF rule per PR, I'm all for it.

@bigcat88
Copy link
Contributor Author

bigcat88 commented Jan 9, 2025

I'll close this PR, since it's big, and it's better to start with smaller rules, like this: #6316

@bigcat88 bigcat88 closed this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants