On May 30, 2011, at 2:35, Christian Heimes <li...@cheimes.de> wrote:
> Am 27.05.2011 23:33, schrieb Andi Vajda: >>> So far the patch is reliable and has improved the stability a lot. I >>> haven't seen a single segfault under Linux X86_64 today. Our test suite >>> has run a dozen times or more. The last five Win32 X86 test runs were >>> stable, too. >> >> I integrated your patch into svn rev 1128467. > > Thank you very much! The patch has proven itself as stable over the last > weeks . I haven't seen a JCC related segfault on our testing and > production servers. > > A while ago I started thread about on python-ideas about the cause of > the issue. I'm working on two PEPs to improve the situation on Python > 3.3, too. Is there anything you want to add to the discussion? I've been following the discussion - I've been cc'ed - and have nothing to add. Your proposal should work nicely, at least for the attach part. I haven't had much luck with detachCurrentThread() in the past. As for Python 3 support, I did a port of jcc to Python 3.2 a while ago and it's been available as an experiment on a branch. I should refresh it to catch up with the latest changes at some point. I don't know what to do about the two version conundrum, when to cut over from Python 2 to Python 3. Supporting both is almost twice the work... Andi.. > > Christian
