This is the mail archive of the
mailing list for the Cygwin project.
Re: [64bit] python3 vs. threads
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 10 Jun 2013 10:32:22 +0200
- Subject: Re: [64bit] python3 vs. threads
- References: <51AD6D64 dot 6040502 at users dot sourceforge dot net> <20130607230754 dot GB5500 at tishler dot net>
- Reply-to: cygwin-apps at cygwin dot com
On Jun 7 19:07, Jason Tishler wrote:
> On Mon, Jun 03, 2013 at 11:30:28PM -0500, Yaakov (Cygwin/X) wrote:
> > As part of the 64bit bootstrap process, I packaged python3, but had
> > to configure it --without-threads due to a runtime error. However,
> > I am finding now that this is not a regularly used configuration;
> > several major Python modules use PyGILState_*() APIs
> > unconditionally, which aren't exported when so configured. Are you
> > able to take a look at the runtime failure and track it down?
> Unfortunately, I don't have access to 64-bit Windows.
You can download a Windows 2012 Evaluation ISO for free from the MSDN
Windows 2012 is always 64 bit, and the evaluation versions works for
180 days for, well, evaluation. It runs fine in VMs.
Does that help?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com