Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Fri, 19 Apr 2002 07:44:17 -0400 From: Jason Tishler Subject: Re: When to release a threaded cygwin Python? In-reply-to: <20020329174418.GD2505@redhat.com> To: cygwin-apps AT cygwin DOT com Mail-followup-to: cygwin-apps AT cygwin DOT com Message-id: <20020419114417.GC1540@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020329130355 DOT GA2520 AT tishler DOT net> <20020329174418 DOT GD2505 AT redhat DOT com> Chris, On Fri, Mar 29, 2002 at 12:44:18PM -0500, Christopher Faylor wrote: > On Fri, Mar 29, 2002 at 08:03:55AM -0500, Jason Tishler wrote: > >Here's the deal. Although a threaded Cygwin Python runs just fine under > >Cygwin 1.3.10, one cannot build one themselves without the following > >patch to sys/features.h: > > > > http://sources.redhat.com/ml/newlib/2002/msg00122.html > > > >So, should I hold off releasing a new Python until 1.3.11? > > Yes. > > I'll release 1.3.11 when Corinna comes back from vacation. Is Corinna back from vacation? :,) Jason