.
K
-Original Message-
From: Python-Dev [mailto:python-dev-
bounces+kristjan=ccpgames@python.org] On Behalf Of Trent Nelson
Sent: 21. desember 2012 03:13
To: Gregory P. Smith
Cc: Python-Dev
Subject: Re: [Python-Dev] Possible GIL/threading issue involving subprocess
Le Fri, 21 Dec 2012 09:31:44 +,
Kristján Valur Jónsson krist...@ccpgames.com a écrit :
I ran into this the other day. I had put in hooks in the
PyMem_MALLOC to track memory per tasklet, and it crashed in those
cases because it was being called without the GIL. My local patch
was simply
On Fri, Dec 21, 2012 at 01:43:11AM -0800, Antoine Pitrou wrote:
Le Fri, 21 Dec 2012 09:31:44 +,
Kristján Valur Jónsson krist...@ccpgames.com a écrit :
I ran into this the other day. I had put in hooks in the
PyMem_MALLOC to track memory per tasklet, and it crashed in those
cases
This seems odd to me so I wanted to see what others think. The unit
test Lib/unittest/test/test_runner.py:Test_TextRunner.test_warnings
will eventually hit subprocess.Popen._communicate.
The `mswindows` implementation of this method relies on threads to
buffer stdin/stdout.
On Thu, Dec 20, 2012 at 10:43 AM, Trent Nelson tr...@snakebite.org wrote:
This seems odd to me so I wanted to see what others think. The unit
test Lib/unittest/test/test_runner.py:Test_TextRunner.test_warnings
will eventually hit subprocess.Popen._communicate.
The
On Thu, Dec 20, 2012 at 05:47:40PM -0800, Gregory P. Smith wrote:
On Thu, Dec 20, 2012 at 10:43 AM, Trent Nelson tr...@snakebite.org
wrote:
This seems odd to me so I wanted to see what others think. The unit
test
