Jens Vagelpohl wrote:
add your comment, encouragement, flames et to the sourceforge bug
tracker issue. i guess that would help most.
I did. What is standard procedure if the situation like the one I've met
appears? What is scenarion from bug report to product release without
the bug
I did. What is standard procedure if the situation like the one I've met
appears? What is scenarion from bug report to product release without the
bug found?
i don't know. the people on the python-dev mailing list could help you with
that question.
jens
Myroslav Opyr wrote:
System Platform
freebsd4
Are you running with the pthread stack size patches applied to Python?
See
https://sourceforge.net/tracker/?func=detailaid=554841group_id=5470atid=305470
for the patch, and recompile Python with
OPT=-g -O2 -DTHREAD_STACK_SIZE=0x2
Hi,
it look like it works! I have to give site some time to run to be sure.
Where I can vote for a bug or to give comments? On SF.tracker issue? to
make it go into release.
As far as I understand the patch is quick-hack to make it work and do not
solve the issue completely, just increase the
add your comment, encouragement, flames et to the sourceforge bug tracker
issue. i guess that would help most.
jens
On Wednesday, May 15, 2002, at 10:55 , Myroslav Opyr wrote:
Hi,
it look like it works! I have to give site some time to run to be sure.
Where I can vote for a bug or to
this particular issue is *not* solved in 2.1.3
jens
On Wednesday, May 15, 2002, at 10:00 , Myroslav Opyr wrote:
As far as I remember the issue was solved in Python 2.1.3, wasn't it? Or
it was GC patch?
Ok, I'll try to patch sources...
m.
--
Myroslav Opyr
zope.net.ua * Ukrainian Zope
