Marcin Juszkiewicz wrote:
> I would say that it is a bit better. Now I at least know that it is
> related to Python 2.5 (which we no longer ship)
It means the problem first showed up with 2.5, but chances are all later 2.x
(and maybe also 3.x) are affected too.
Kevin Kofler