Message339481
| Author |
gregory.p.smith |
| Recipients |
cagney, gregory.p.smith, ned.deily, vstinner |
| Date |
2019年04月05日.09:02:41 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1554454961.3.0.297805315579.issue36533@roundup.psfhosted.org> |
| In-reply-to |
| Content |
A stdlib alternative to this whole mess would be to avoid acquiring the logging locks before fork() as we currently do and just blindly re-initialize all of them afterwards under the assumption that they "can't" be protecting anything in a newly forked child process. Handlers that need specific resource synchronization around fork would then be required to deal with their own os.register_at_fork() calls. (ex: to avoid multiple processes writing to the same file or fd at once) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年04月05日 09:02:41 | gregory.p.smith | set | recipients:
+ gregory.p.smith, vstinner, ned.deily, cagney |
| 2019年04月05日 09:02:41 | gregory.p.smith | set | messageid: <1554454961.3.0.297805315579.issue36533@roundup.psfhosted.org> |
| 2019年04月05日 09:02:41 | gregory.p.smith | link | issue36533 messages |
| 2019年04月05日 09:02:41 | gregory.p.smith | create |
|