Martin v. Löwis <[EMAIL PROTECTED]> added the comment: 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. ---------- nosy: +loewis _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3235> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
