New issue
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
Is contextlib.redirect_stdout reentrant or not? #65260
Comments
The docs are contradictory on whether or not contextlib.redirect_stdout is reentrant, or reusable-but-not-reentrant. This would seem to be an oversight from bpo-19403, which probably should have changed "reusable but not reentrant" to "reentrant". Present in both current and upcoming docs: contextlib.redirect_stdout(new_target)
...
This context manager is reusable but not reentrant. 29.6.3.1. Reentrant context managers |
Indeed, it is actually reentrant now - the part that claims it isn't needs to be tweaked appropriately. |
Here is a simple patch to correct the redirect_stdout documentation. |
New changeset dafbd78ac15b by Nick Coghlan in branch '3.4': New changeset 83540d7b7366 by Nick Coghlan in branch 'default': |
Thanks folks - the outdated cross reference has been updated as Berker suggested. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: