Am 10.01.2013 11:48, schrieb Antoine Pitrou: > Having an official afterfork facility would still help. I currently > rely on multiprocessing.util.register_after_fork(), even though it's an > undocumented API (and, of course, it works only for those child > processes launched by multiprocessing, not other fork() uses). The time machine strikes again: http://bugs.python.org/issue16500
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4