anatoly techtonik <techtonik <at> gmail.com> writes: > > Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing > in Windows I would vote for more time for stabilizating things - not > adding new features. Long awaited subprocess as replacement for > os.popen() AFAIK is still incapable to asynchronously communicate with > spawned processes on Windows. I would call this feature as critical > even on 2.6 As a release testcase - try porting pyexpect module to > this platform. Absence of native curses/console/readline module also > makes Python one-way unix shell language while many users expect it to > be crossplatform. As always, patches and proposals are welcome! However, as far as the above issues are concerned, it seems to be less a matter of time between releases than of motivation to get things done (tm). I don't think a knowledgeable and determined Windows programmer would have much trouble solving each of them. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4