A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-March/002527.html below:

Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted?

[Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted? [Python-Dev] FW: Fixing os.popen on Win32 => is the win32pipe stuff going to be adopted?Fred L. Drake, Jr. fdrake@acm.org
Thu, 9 Mar 2000 09:25:35 -0500 (EST)
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.


  -Fred

--
Fred L. Drake, Jr.	  <fdrake at acm.org>
Corporation for National Research Initiatives



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