Berker Peksag added the comment:
Here is a simple patch to correct the redirect_stdout documentation.
--
keywords: +patch
nosy: +berker.peksag
stage: - patch review
Added file: http://bugs.python.org/file36877/issue21061.diff
___
Python tracker
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: docs@python - rhettinger
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21061
___
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: rhettinger - ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21061
___
Roundup Robot added the comment:
New changeset dafbd78ac15b by Nick Coghlan in branch '3.4':
Issue #21061: correctly note redirect_stdout is reentrant
https://hg.python.org/cpython/rev/dafbd78ac15b
New changeset 83540d7b7366 by Nick Coghlan in branch 'default':
Merge issue #21061 fix from 3.4
Nick Coghlan added the comment:
Thanks folks - the outdated cross reference has been updated as Berker
suggested.
--
resolution: - fixed
stage: patch review - resolved
status: open - closed
type: - enhancement
___
Python tracker
New submission from Timothy Pederick:
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 issue19403, which probably should have changed reusable but not
reentrant to reentrant.
Present
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21061
___
___
Python-bugs-list
Nick Coghlan added the comment:
Indeed, it is actually reentrant now - the part that claims it isn't needs to
be tweaked appropriately.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21061
