Re: When to release a threaded cygwin Python?

2002-04-19 Thread Corinna Vinschen 

On Fri, Apr 19, 2002 at 07:44:17AM -0400, Jason Tishler wrote:
> 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? :,)

Physically or psychically?  ;-)

Corinna

Re: When to release a threaded cygwin Python?

2002-04-19 Thread Jason Tishler 

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

Re: When to release a threaded cygwin Python?

2002-03-29 Thread Christopher Faylor 

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

When to release a threaded Cygwin Python?

2002-03-29 Thread Jason Tishler 

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