<font face="arial" size="3">I am in the process of implementing a
number of often requested features and proposed patches in the subprocess
module for my Google Summer of Code 2009 project. For information on
my progress, check out my blog located at </font><a href="http://subdev.blogspot.com/" target="_blank"><font color="#0000ff" face="arial" size="3"><u>http://subdev.blogspot.com/</u></font></a><font face="arial" size="3">. Any comments and suggestions are greatly appreciated.</font><br>
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
> Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing<br>
> in Windows I would vote for more time for stabilizating things - not<br>
> adding new features. Long awaited <span class="il">subprocess</span> as replacement for<br>
> os.<span class="il">popen</span>() AFAIK is still incapable to asynchronously communicate with<br>
> spawned processes on Windows. I would call this feature as critical<br>
> even on 2.6 As a release testcase - try porting pyexpect module to<br>
> this platform. Absence of native curses/console/readline module also<br>
> makes Python one-way unix shell language while many users expect it to<br>
> be crossplatform.<br><br>
I am not quite sure whether you are for new features or not. Your<br>
first sentence ("vote for ... not adding new features") seems to<br>
suggest that you would not like to see new features, and your last<br>
sentence ("absence of native curses/console/readline module")<br>
suggests that you *do* want to see new features (namely, a native<br>
curses module, and a native readline module).<br><br>
Which one is it?<br><br>
Regards,<br>
Martin<br></blockquote>