We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The documentation for werkzeug.test.Client says it expects a subclass of TestResponse, failing which it will construct the subclass:
werkzeug.test.Client
TestResponse
werkzeug/src/werkzeug/test.py
Lines 778 to 780 in 5ff0a57
However, the implementation is using isinstance instead of issubclass:
isinstance
issubclass
Lines 812 to 817 in 5ff0a57
The problem was introduced in commit 669323c (specific lines) so it's been around since the 2.0 release.
The text was updated successfully, but these errors were encountered:
Fix: Use issubclass instead of isinstance
7ab3823
Bug described at #2831
Successfully merging a pull request may close this issue.
The documentation for
werkzeug.test.Client
says it expects a subclass ofTestResponse
, failing which it will construct the subclass:werkzeug/src/werkzeug/test.py
Lines 778 to 780 in 5ff0a57
However, the implementation is using
isinstance
instead ofissubclass
:werkzeug/src/werkzeug/test.py
Lines 812 to 817 in 5ff0a57
The problem was introduced in commit 669323c (specific lines) so it's been around since the 2.0 release.
The text was updated successfully, but these errors were encountered: