"Fred L. Drake, Jr." wrote:
>
> Tim Peters writes:
> > Failing that, the os.popen docs should caution it's "use at your own risk"
> > under Windows, and that this is directly inherited from MS's popen
> > implementation.
>
> Tim (& others),
> Would this additional text be sufficient for the os.popen()
> documentation?
>
> \strong{Note:} This function behaves unreliably under Windows
> due to the native implementation of \cfunction{popen()}.
>
> If someone cares to explain what's weird about it, that might be
> appropriate as well, but I've never used this under Windows.
Ehm, hasn't anyone looked at the code I posted yesterday ?
It goes a long way to deal with these inconsistencies... even
though its not perfect (yet ;).
--
Marc-Andre Lemburg
______________________________________________________________________
Business: http://www.lemburg.com/
Python Pages: http://www.lemburg.com/python/
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