git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Work around performance bug in subprocess.Popen.communicate()

From
ESErik Sandberg <mandolaerik@gmail.com>
Date
Aug 14, 2009, 07:26 UTC
Message-ID
<e87cdfda0908140026x21b8aad3x82417d4b1c8016f4@mail.gmail.com>
In-Reply-To
<20090814062149.GA23179@lux.e.vtech>
On Fri, Aug 14, 2009 at 8:21 AM, Karl Wiberg<kha@virtutech.com> wrote:
Show 6 quoted lines
> On 2009-08-13 23:18:59 +0100, Catalin Marinas wrote:
>
>> Since we are only using Git, I'll merge this patch
>> (and maybe add a comment).
>
> Sure.

Wouldn't it be better to only use the write() workaround when sys.version indicates that the Python bug may be present, and use communicate() properly otherwise?

Erik
Previous: Karl WibergNext: Karl Wiberg
Message 6 of 7 in “Work around performance bug in subprocess.Popen.communicate()”
  1. Work around performance bug in subprocess.Popen.communicate()Karl Wiberg, Jul 31, 2009
  2. Catalin MarinasJul 31, 2009
  3. Karl WibergAug 4, 2009
  4. Catalin MarinasAug 13, 2009
  5. Karl WibergAug 14, 2009
  6. Erik SandbergAug 14, 2009
  7. Karl WibergAug 14, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.