Walker Hale IV added the comment:
Clarifying the documentation regarding the __enter__ method eliminates the need
for further discussion on this point regarding pop_all(), which was really just
the motivating use case.
That leaves the question of the most readable documentation change that
Walker Hale IV added the comment:
This one-line patch should clarify the point.
--
___
Python tracker
<http://bugs.python.org/issue28516>
___
___
Python-bug
Changes by Walker Hale IV :
--
assignee: -> docs@python
components: +Documentation
keywords: +patch
nosy: +docs@python
Added file: http://bugs.python.org/file45206/issue28516.diff
___
Python tracker
<http://bugs.python.org/issu
New submission from Walker Hale IV:
contextlib.ExitStack implies but does not explicitly state that its __enter__
method trivially returns self.
This means that if a user invokes pop_all and then uses the resulting ExitStack
instance in a with statement, the user will be relying on
