Antoine Pitrou pit...@free.fr added the comment:
Actually, it's probably a duplicate of #7105.
--
resolution: - duplicate
status: open - closed
superseder: - weak dict iterators are fragile because of unpredictable GC runs
___
Python tracker
Changes by Jesse Noller jnol...@gmail.com:
--
priority: - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3578
___
___
Python-bugs-list
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Mmmh, the problem with the list(X.items()) idiom is that it's
thread-safe only if X.items() is implemented in C. Otherwise X can be
mutated if there is a thread-switch while executing bytecode in X.items().
In weakref.py (line 103), by
Ismail Donmez [EMAIL PROTECTED] added the comment:
py3k branch gives another error now, when running test_multiprocessing
in a tight loop:
test test_multiprocessing failed -- Traceback (most recent call last):
File /Users/cartman/Sources/py3k/Lib/test/test_multiprocessing.py,
line 1163, in
Jesse Noller [EMAIL PROTECTED] added the comment:
Ismail, that's the incref bug in issue 3419
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3578
___
___
Ismail Donmez [EMAIL PROTECTED] added the comment:
Ah cool, we might be at the end of multiprocessing problems then I guess
:-)
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3578
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Le lundi 18 août 2008 à 19:42 +, Ismail Donmez a écrit :
Ismail Donmez [EMAIL PROTECTED] added the comment:
Ah cool, we might be at the end of multiprocessing problems then I guess
:-)
Well, not really, it should be diagnosed why the
New submission from Mark Dickinson [EMAIL PROTECTED]:
Here's a report from Ismail Donmez (cartman), extracted from the
issue 3419 discussion in an effort to avoid putting multiple
problems under one tracker issue.
[cartman]
With trunk when running test_multiprocessing in a tight loop I saw
