Dear IronPython gurus!
Hopping you can help me with a kind of ramdom bug (unexpected
SystemError and ValueError exception) in _weakrefset.py (it would be
great if you can replicate it by running my script below. Please let me
know).
The error is random, but I managed to reproduce it by running th
I confirm the same problem, except that it happens more often for me, about 50
to 60 times each time I run the test.
It smells like some sort of “unsynchronised acess by different threads to an
object problem ”.
One (very) hacky way round it until the real cause is established is to modify
__
Thank you Andrew, good to know you could replicate it. I went to very
similar workarround with __contains__(), but yours is more elegant with the
"while 1". However, I will recommend to repeat only a few times (to avoid a
possible endless loop) and to catch the two unexpected exception only
(System
did anybody try it with the 2.7.4?
I wonder it is something we introduced in 2.7.5.
--pawel
On Mon, Apr 13, 2015 at 6:29 PM, Andres Sommerhoff wrote:
> Thank you Andrew, good to know you could replicate it. I went to very
> similar workarround with __contains__(), but yours is more elegant with t
Hi Pawel, its actually very old to me (more than a year). I'm suffering
gradually as the code went more complex. At the beginning was not a big issue.
Now, it is not a chance to run some code under IronPython without the weakref
exception (so Im running it in Cpython or with the workarround of m
