Improve the type safety of errorinfo.ReportException
.
#823
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.
Due to the possibility that
sys.exc_info()[2]
andTracebackType.tb_next
may returnNone
, there are points inerrorinfo.ReportException
where the type checker will produce errors.If this function is called with a specified
stacklevel
without catching an error, or ifstacklevel
is specified deeper than the cause of the error even when an error is caught, anAttributeError
will be raised.By explicitly detecting such cases and throwing a
ValueError
, the implementation oferrorinfo.ReportException
can be made type-safe.