From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32065 invoked by alias); 23 Jul 2009 04:55:53 -0000 Received: (qmail 32054 invoked by uid 22791); 23 Jul 2009 04:55:52 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from qw-out-1920.google.com (HELO qw-out-1920.google.com) (74.125.92.144) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Jul 2009 04:55:46 +0000 Received: by qw-out-1920.google.com with SMTP id 5so354207qwc.20 for ; Wed, 22 Jul 2009 21:55:44 -0700 (PDT) Received: by 10.224.61.4 with SMTP id r4mr1595422qah.349.1248324943964; Wed, 22 Jul 2009 21:55:43 -0700 (PDT) Received: from ?192.168.0.101? (S010600112f237275.wp.shawcable.net [24.76.241.98]) by mx.google.com with ESMTPS id 6sm1685934qwk.14.2009.07.22.21.55.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 22 Jul 2009 21:55:42 -0700 (PDT) Message-ID: <4A67ED57.3070300@users.sourceforge.net> Date: Thu, 23 Jul 2009 12:18:00 -0000 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: python 2.6 References: <49688D6D.9060108@gmail.com> <496BEB8D.60802@gmail.com> <20090113171258.GA1104@tishler.net> <49792F5F.5020409@users.sourceforge.net> <20090126152024.GC8368@tishler.net> In-Reply-To: <20090126152024.GC8368@tishler.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-07/txt/msg00839.txt.bz2 On 26/01/2009 09:20, Jason Tishler wrote: > I don't know, but building Python 2.6 with openssl support causes the > treading related operations to core dump. Maybe this particular code > path tickles a problem in Cygwin? For some reason, Python 2.5.2 and 3.0 > do not exhibit the same behavior. It seems the correlation is that in 2.6, _ssl itself uses threads; in 2.5 it did not, but in 3.1 it does and those same tests pass, as they do if _ssl.dll is not present in 2.6. I don't know the cause but I did find an easy workaround: Forcefully disabling threads in _ssl.c by adding #undef WITH_THREAD immediately after #include "Python.h" creates a _ssl.dll that allows the tests to pass. While this may seem a bit crude, it's really the same situation that existed in 2.5, where the core is threaded and _ssl isn't thread-aware. As for updating Cygwin's python to 2.6, I see that 2.5 is the default version in stable and up, with 2.6/3.1 available only in experimental. I suggest we do similarly; leave the distro default at 2.5.4 (rebuilt for 1.7) and add non-default (IOW nothing non-versioned in /usr/bin) python2.6 and python3.1 packages for users to try. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple