Bugfix unprintable assertion errors #2284
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs:
master
; for new features, targetfeatures
;Unless your change is trivial documentation fix (e.g., a typo or reword of a small section) please:
AUTHORS
;CHANGELOG.rst
CHANGELOG
, so please add a thank note to yourself ("Thanks @user for the PR") and a link to your GitHub profile. It may sound weird thanking yourself, but otherwise a maintainer would have to do it manually before or after merging instead of just using GitHub's merge button. This makes it easier on the maintainers to merge PRs.The error I am fixing is one that I encountered when using a rather badly written python package I was forced to use as - is. One of the classes defined in the package decided to return unprintable strings as the result of its'
__repr__
method. This causedpy._builtin._totext
to throw an error in python2.7, since it's actually the functionunicode
which cannot decode strings outside of range 128. Also using_totext
was unsafe in python3 as well, since classes with throwing__repr__
methods should not cause internal errors and stop all other tests from running.I know that the event of both raising an
AssertionError
(instead of usingassert
) and the__repr__
method being unsafe is rather rare and points to horrific code, but it happened to me nonetheless, using code that is out of my control, and it should not cause internal errors imo.Error reproduction: