Serhiy Storchaka added the comment:

The one of potential advantages of the API proposed by Gregory is that 
os.register_at_fork() can be made atomic. Either register all callbacks, or do 
nothing in the case of error. But current proposed implementation is not 
atomic. If resizing of some list is failed due to MemoryError (or may be 
KeyboardInterrupt), some callbacks can already be registered.

Is it worth to guarantee the atomicity of os.register_at_fork().

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16500>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to