Re: Getting ready for 3.2 beta 2

I've been away this weekend - just got back, but I'm too busy to try to read all the multiple-interpreter related comments. I guess my question is - can someone provide a quick summary of how far we are from 3.2.1b test tarbal? Thanks! Grisha On Thu, 1 Sep 2005, Graham Dumpleton wrote: N

Re: Getting ready for 3.2 beta 2

Well, if I've understood Jim's mail, apart from the new MODPYTHON-77, we're all set. Regards, Nicolas2005/9/6, Gregory (Grisha) Trubetskoy <[EMAIL PROTECTED]>: I've been away this weekend - just got back, but I'm too busy to try toread all the multiple-interpreter related comments. I guess my ques

Re: Getting ready for 3.2 beta 2

Gregory (Grisha) Trubetskoy wrote: I've been away this weekend - just got back, but I'm too busy to try to read all the multiple-interpreter related comments. I guess my question is - can someone provide a quick summary of how far we are from 3.2.1b test tarbal? I've also been away for the

Re: Getting ready for 3.2 beta 2

On Tue, 6 Sep 2005, Jim Gallacher wrote: As Graham stated on the weekend, "the use of thread states can be very tricky". I think we should proceed with the 3.2.1b without the fix. That way we can take the time to make sure we understand the issues and fix it in 3.3. If that seems reasonable,

[jira] Commented: (MODPYTHON-77) The multiple interpreter concept of mod_python is broken for Python extension modules since Python 2.3

[ http://issues.apache.org/jira/browse/MODPYTHON-77?page=comments#action_12322779 ] Jim Gallacher commented on MODPYTHON-77: Boyan, src.zip (file attachment 8) passes the unit tests for mpm-prefork on linux with python 2.3.5. I haven't tested it o