18 May
2002
18 May
'02
9:01 a.m.
You should be running 2.4.4 or 2.5.1. This is a known bug in 2.4.3. (It only shows up under python 2.1.3 or later - earlier versions of python silently corrupt memory).
it actually showed up under 2.1.2, but that had bugs of its own in this area ;-)
It very nice to hear that I can simply upgrade and my problem will go away :) And it did! Just thought I'd mention this since I didn't find anything in the collector about it. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za