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 found? m.
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 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 stack size... There should be better solution, isn't it?
Will it go into Python-2.1.4?
m. -- Myroslav Opyr zope.net.ua * Ukrainian Zope Hosting e-mail: myroslav@zope.net.ua cell: +380 50.3174578
On Wed, 15 May 2002, Behrens Matt - Grand Rapids wrote:
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?
No.
Try my patch, that solves the problem Jens is talking about.
-- Myroslav Opyr zope.net.ua <http://zope.net.ua/> ° Ukrainian Zope Hosting e-mail: myroslav@zope.net.ua <mailto:myroslav@zope.net.ua> cell: +380 50.3174578