This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients brian.curtin, gregory.p.smith, neologix, pitrou
Date 2011-05-11.08:57:50
SpamBayes Score 2.407522e-08
Marked as misclassified No
Message-id <BANLkTimXGdZttwdqj9dvnG0Y2F_tzoVvkA@mail.gmail.com>
In-reply-to <BANLkTinRDu0_r7fNPT4Aov=GpCVFybm-4A@mail.gmail.com>
Content
I didn't initially like the idea of __exit__ blocking on another
process... but the zombie issue is real does make me think we should
reconsider this and have it wait().

It is a backwards incompatible change if anyone has started using the
Popen context manager to launch a long running subprocess that they
did not want to wait for.  That should be exceedingly rare.

I say change the behavior to wait() in 3.3, 3.2.1 and 2.7.2.  Keep the
note in the documentation and turn it into something that stands out
better like a note or a warning suggesting that people always call
wait() after the Popen context manager exits if they need to be
compatible with 2.7.1 or earlier.
History
Date User Action Args
2011-05-11 08:57:51gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, brian.curtin, neologix
2011-05-11 08:57:51gregory.p.smithlinkissue12044 messages
2011-05-11 08:57:50gregory.p.smithcreate