Message365952
| Author |
melwitt |
| Recipients |
gregory.p.smith, melwitt, vinay.sajip, vstinner |
| Date |
2020年04月07日.22:13:16 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1586297597.24.0.350352157542.issue40091@roundup.psfhosted.org> |
| In-reply-to |
| Content |
Hi, I've been following the work related to:
https://bugs.python.org/issue6721
https://bugs.python.org/issue40089
because I encountered a problem where a standard library lock was held by a parent process at the time that child processes were forked, so the child processes got stuck behind the inherited held locks.
But, if I'm understanding correctly, this issue is fixing something in python logging specifically and not all standard library locks in general.
My question is, will there be a way to reinit standard library locks in general using _at_fork_reinit()? That is, should we expect a future fix in python to do this or is the recommendation to continue to ensure the application reinits locks during process start if we know the process could be a child?
Thanks for your advice. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2020年04月07日 22:13:17 | melwitt | set | recipients:
+ melwitt, gregory.p.smith, vinay.sajip, vstinner |
| 2020年04月07日 22:13:17 | melwitt | set | messageid: <1586297597.24.0.350352157542.issue40091@roundup.psfhosted.org> |
| 2020年04月07日 22:13:17 | melwitt | link | issue40091 messages |
| 2020年04月07日 22:13:16 | melwitt | create |
|