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

deprecate the --diff option #1441

Merged
merged 1 commit into from
Nov 6, 2021
Merged

Conversation

asottile
Copy link
Member

@asottile asottile commented Nov 6, 2021

resolves #1389

@sigmavirus24 sigmavirus24 merged commit e34647f into PyCQA:main Nov 6, 2021
@asottile asottile deleted the deprecate_diff branch November 6, 2021 12:56
@noamraph
Copy link

@asottile I would vote to un-deprecate this feature. I'm trying to improve the code style in my company, and as a first step I want to forbid commits that add new warnings. I hope that in the future I will be able to fix all style issues, but that will take a (long) while. Using the --diff option seems like the only way to prevent new style violations from being committed.

I understand that --diff is not perfect, as new warnings can be triggered. However, as it's a very useful feature, I suggest to replace the deprecation with a note explaining why new warnings might be introduced even if flake8 --diff didn't show anything.

@asottile
Copy link
Member Author

it's fundamentally broken so it is being removed

I recommend you either:

  • use a code formatter to fix the existing issues
  • work file-by-file to fix issues

more on that: https://github.com/readme/guides/code-review

@PyCQA PyCQA locked as resolved and limited conversation to collaborators Jan 23, 2022
@asottile asottile added this to the 5.0.0 milestone Jul 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Current implementation of --diff is kind of broken by design
3 participants