Message 124657 - Python tracker

➜

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	eric.araujo
Recipients	docs@python, eric.araujo, gregory.p.smith, steven.k.wong
Date	2010-12-26.01:58:57
SpamBayes Score	0.0061830147
Marked as misclassified	No
Message-id	<1293328740.75.0.204805336955.issue7678@psf.upfronthosting.co.za>
In-reply-to

Content
As a non-expert user of subprocess, calling close before communicate seems strange to me. Does the example code with a bug work if close is called after communicate? In the 3.2 docs, we could update the example to use a with statement, unless it is deemed a distraction for this simple introductory section.

As a non-expert user of subprocess, calling close before communicate seems strange to me.  Does the example code with a bug work if close is called after communicate?

In the 3.2 docs, we could update the example to use a with statement, unless it is deemed a distraction for this simple introductory section.

History
Date	User	Action	Args
2010-12-26 01:59:00	eric.araujo	set	recipients: + eric.araujo, gregory.p.smith, steven.k.wong, docs@python
2010-12-26 01:59:00	eric.araujo	set	messageid: <1293328740.75.0.204805336955.issue7678@psf.upfronthosting.co.za>
2010-12-26 01:58:57	eric.araujo	link	issue7678 messages
2010-12-26 01:58:57	eric.araujo	create