Message 11995 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	tim.peters
Date	2002年08月16日.15:26:56
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
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.

Content

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.

History
Date	User	Action	Args
2007年08月23日 14:04:57	admin	link	issue595601 messages
2007年08月23日 14:04:57	admin	create

homepage