delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2002/03/29/07:58:28

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 08:03:55 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: When to release a threaded Cygwin Python?
To: Cygwin-Apps <cygwin-apps AT cygwin DOT com>
Mail-followup-to: Cygwin-Apps <cygwin-apps AT cygwin DOT com>
Message-id: <20020329130355.GA2520@tishler.net>
MIME-version: 1.0
User-Agent: Mutt/1.3.24i

I would like to release a threaded Cygwin Python.  However, I would like
to avoid another fiasco like my last PostgreSQL release... :,)

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?  Or, is it
OK to release one now with the appropriate build caveat documented in
the README?

Thanks,
Jason

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019