Myroslav Opyr wrote:
For FreeBSD there is another pthreads related bug in Python. And
quick-patch from
https://sourceforge.net/tracker/?func=detailaid=554841group_id=5470atid=305470
with THREAD_STACK_SIZE=0x2 solves the problem. But it is quick and
dirty hack. Will it be solved in
Matthew T. Kromer wrote:
Myroslav Opyr wrote:
For FreeBSD there is another pthreads related bug in Python. And
quick-patch from
https://sourceforge.net/tracker/?func=detailaid=554841group_id=5470atid=305470
with THREAD_STACK_SIZE=0x2 solves the problem. But it is quick
and dirty
Matthew T. Kromer wrote:
Ahsan Imam wrote:
I was going through the zope archive mail and saw message posted by
Matthew T. Kromer regarding crashing problems with Python 2.1.2. It
instructed to increase the #define PyTrash_UNWIND_LEVEL from 50 500.
I just downloaded python 2.1.3. Do I
Hello,
I was going through the zope archive mail and saw message posted by
Matthew T. Kromer regarding crashing problems with Python 2.1.2. It
instructed to increase the
#define PyTrash_UNWIND_LEVEL from 50 500.
I just downloaded python 2.1.3. Do I still have to edit the object.h
file
Ahsan Imam wrote:
Hello,
I was going through the zope archive mail and saw message posted by
Matthew T. Kromer regarding crashing problems with Python 2.1.2. It
instructed to increase the
#define PyTrash_UNWIND_LEVEL from 50 500.
I just downloaded python 2.1.3. Do I still have to edit
From: Ahsan Imam [EMAIL PROTECTED]
I just downloaded python 2.1.3. Do I still have to edit the object.h
file before I compile it.
no, 2.1.3 includes bugfixes that specifically address those issues.
/dario
___
Zope-Dev maillist - [EMAIL
