[pypy-issue] Issue #2179: open() blocks the thread, but only in a module, until the main module is ...finished? (pypy/pypy)
issues-reply at bitbucket.org
Thu Oct 29 23:40:54 EDT 2015
New issue 2179: open() blocks the thread, but only in a module, until the main module is ...finished?
When I try to open a file in a thread, the call to open() blocks until my main thread has fallen off and run out of code. But only if that code was loaded from a module. It produces a deadlock if the main thread depends on any results from the thread subsequent to that call to open(), severely limiting what I/O a thread can do with the main thread blocking all open() calls from completing.
Tried it on pypy3, not a problem on pypy2 apparantly.
Python 3.2.5 (b2091e973da69152b3f928bfaabd5d2347e6df46, Sep 10 2015, 00:16:16)
I can't compile the latest python. (3 hours compiling, then 70 pages of compiler warnings, with an error somewhere in there)
More information about the pypy-issue