Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Date:	Fri, 29 Mar 2002 12:44:18 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: When to release a threaded cygwin Python?
Message-ID:	<20020329174418.GD2505@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<20020329130355 DOT GA2520 AT tishler DOT net>
Mime-Version:	1.0
In-Reply-To:	<20020329130355.GA2520@tishler.net>
User-Agent:	Mutt/1.3.23.1i

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.

cgf

- Raw text -