-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
write directly to sys.stdout.buffer to avoid windows io encoding #1382
Conversation
@@ -130,21 +125,15 @@ def test_write_uses_an_output_file(tee): | |||
] | |||
|
|||
|
|||
@mock.patch("flake8.formatting.base.print") | |||
def test_write_uses_print(print_function): | |||
def test_write_uses_print(capsys): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should rename this too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh yeah good point!
Flake8 throws AttributeError on this line now. Any suggestions? https://github.com/KSP-CKAN/NetKAN-Infra/pull/228/checks?check_run_id=3886107937
|
Why the downthumbs on my previous comment, @asottile and @sigmavirus24? Line 187 of |
because you failed to look at pinned issues or do any due diligence and you're using an unsupported private api |
I'm not using any API, I'm just running pytest with this in [pytest]
addopts = -p no:cacheprovider --mypy --pylint --flake8 I've looked at the pinned issue. It says something about monkeypatching I guess the key takeaway here is that people are having flake8 break on them without themselves commiting whatever heinous technical sin so offends you here, because apparently pytest did it. I would suggest reconsidering how you are approaching that segment of your user base. |
it's not pytest either, place your blame on pytest-flake8 also please adjust your attitude |
resolves #1381