Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 24 Sep 2001 09:00:43 -0400 From: Jason Tishler To: Robert Collins Cc: cygwin-developers AT cygwin DOT com, Norman Vine Subject: Re: 1.3.4? Message-ID: <20010924090043.K1904@dothill.com> Mail-Followup-To: Robert Collins , cygwin-developers AT cygwin DOT com, Norman Vine Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Rob, On Mon, Sep 24, 2001 at 02:06:04PM +1000, Robert Collins wrote: > > From: Jason Tishler [mailto:jason AT tishler DOT net] > > I'm leaning toward holding off releasing a threaded Python until your > > muto upgrade in complete. Do you concur? > > So it's up to you really. I don't know when I'll get it done, (all my > current hack time is on the daemon/setup). How often does it occur? Is > it in the test suite only? So far, the only time that I use the threading in threaded Python is when I run the regression test. I have only seen the hang is one thread related regression test: test_threadedtempfile.py. This test spawns a lot of threads which I guess increases the probability that a hang occurs. Maybe under normal conditions, the race condition won't happen too frequently (of course, until I release a threaded Python...). Norman, would you care to comment on the above? Do you use threaded Cygwin Python? If so, have you seen this or other thread related hangs? Thanks, Jason