[3.8] bpo-35753: Fix crash in doctest with unwrap-able functions #22834
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.
Doctest needs to Ignore objects that inspect.unwrap throws ValueError due to "infinite" nesting.
This case is relatively commonly reproduced by importing unittest.mock.call into a module's namespace.
The following code produces a module that will crash doctest:
This is due to the call to unwrap throwing an uncaught ValueError.
For this case we can simply ignore the function and not attempt to extract docstring from this function.
This diff is intentionally done as a branch with two commits to provide failing test case and then a fix to show the problem is contained.
Future thoughts:
id
some objects so that future objects that cause problems with doctest can be passed in to ignore?Note: This branch diff will need to be pulled up into 3.9 and master as the bug exists in those branches as well.
https://bugs.python.org/issue35753