This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tomMoral
Recipients davin, pitrou, tomMoral
Date 2018-01-13.18:06:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Is it an optimization problem, or does it risk leaking semaphores?

I do not think it risks leaking semaphores as the clean-up is performed by the process which created the Semaphore. So I would say it is more an optimization issue.

It is true that I do not see many use case where the Semaphore might be created by the child process but it was optimized in previous version. If you don't think it is useful, we could avoid sharing the semaphore_tracker pipe to the child process to reduce complexity in the spawning process. Do you think it is worth fixing or it should be simplified?
Date User Action Args
2018-01-13 18:06:23tomMoralsetrecipients: + tomMoral, pitrou, davin
2018-01-13 18:06:23tomMoralsetmessageid: <>
2018-01-13 18:06:23tomMorallinkissue31310 messages
2018-01-13 18:06:23tomMoralcreate