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 | loewis |
|---|---|
| Recipients | dwblas, georg.brandl, loewis, mmokrejs |
| Date | 2008年06月29日.17:29:07 |
| SpamBayes Score | 0.011745348 |
| Marked as misclassified | No |
| Message-id | <1214760549.31.0.890839188648.issue3235@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
1. The documentation never gives a rationale for deprecating things. To find out why they are deprecated, you'll typically have to research what checkins to a code base have been made that added the deprecation, and perhaps also ask on mailing lists. For the regular developer, the rationale for deprecation should be irrelevant, as he needs to change his code to drop usage of the deprecated API, anyway. 2. You really need to read all of the documentation, in particular the section that talks about stdin,stdout,stderr in http://docs.python.org/lib/node528.html In the example, stdin is inherited from the parent process. Read the documentation to find out how to send data to the first process. 3. It is not true that this is nowhere explained. http://docs.python.org/lib/node532.html explains precisely what the semantics of communicate is. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月29日 17:29:09 | loewis | set | spambayes_score: 0.0117453 -> 0.011745348 recipients: + loewis, georg.brandl, mmokrejs, dwblas |
| 2008年06月29日 17:29:09 | loewis | set | spambayes_score: 0.0117453 -> 0.0117453 messageid: <1214760549.31.0.890839188648.issue3235@psf.upfronthosting.co.za> |
| 2008年06月29日 17:29:08 | loewis | link | issue3235 messages |
| 2008年06月29日 17:29:07 | loewis | create | |