Message11995
Logged In: YES
user_id=31435
To cheer you up, it's probably worse than that <wink>.
While you're holding a file lock, in theory you dare not
execute any code that may call back into Python, because
the called code may try to do an operation on the file
you've got locked, and then the whole system freezes. That
is, independent of the GIL, it's not thoroughly safe to call
PyObject_Print with a file lock held, because an object's
__str__ may try to "do something" with the Python-level file
object too. The more depressing news is that a reentrant
file lock would solve that one. |
|
Date |
User |
Action |
Args |
2007-08-23 14:04:57 | admin | link | issue595601 messages |
2007-08-23 14:04:57 | admin | create | |
|