
report at bugs
Jun 11, 2008, 4:57 PM
Post #4 of 5
(223 views)
Permalink
|
|
[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()
[In reply to]
|
|
Adam Olsen <rhamph [at] gmail> added the comment: Incidentally, it doesn't seem necessary to reinitialize the lock. Posix duplicates the lock, so if you hold it when you fork your child will be able to unlock it and use it as normal. Maybe there's some non-Posix behaviour or something even more obscure when #401226 was done? (reinitializing is essentially harmless though, so in no way should this hold up release.) _______________________________________ Python tracker <report [at] bugs> <http://bugs.python.org/issue1683> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|