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
twisted.web generates deprecation warnings internally #12172
Comments
I hope you mean "should not be mangled like"? |
Indeed I did! Fixed. |
Thanks. I feel like we need some support from trial to catch all warnings and have an option to fail on warnings. I think that something like this is availabe in pytest. I tried to search the GitHub Issues but I could not find any existing ticket/issue for trial for such a feature. Do you think it would help ? |
@adiroiban I think that #6348 is that ticket. Before we can enforce this in CI we have a lot of cleanup to do, though. |
Describe the incorrect behavior you saw
The
twisted.web
tests fail whenDeprecationWarning
is made an error.FAILED (skips=4, errors=22, successes=541)
Describe how to cause this behavior
Run the tests like:
Describe the correct behavior you'd like to see
Twisted should not generate deprecation warnings internally (see also #6348).
Also, the deliberate warnings should not be mangled like "twisted.web.resource._UnsafeNoResource.__init__ was deprecated in Twisted 22.10.0; please use Use twisted.web.pages.notFound instead, which properly escapes HTML. instead".
The text was updated successfully, but these errors were encountered: