You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, it's relatively obvious that the note call is the culprit. But it may be more confusing in more complicated functions, since that information gets trimmed from the traceback.
I propose we either:
fail early and explicitly when note is passed a non-str value
automatically coerce note(x) to report(str(x)) instead of report(x)
Consider the following:
This errors with the following traceback:
In this case, it's relatively obvious that the
notecall is the culprit. But it may be more confusing in more complicated functions, since that information gets trimmed from the traceback.I propose we either:
noteis passed a non-str valuenote(x)toreport(str(x))instead ofreport(x)This came up in practice in
hypothesis/hypothesis-python/tests/nocover/test_explore_arbitrary_languages.py
Lines 115 to 120 in 798803a
The text was updated successfully, but these errors were encountered: