Message 235404 - Python tracker

➜

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	vstinner
Recipients	dan.oreilly, gvanrossum, vstinner, yselivanov
Date	2015-02-04.21:06:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1423083994.08.0.392740496312.issue22087@psf.upfronthosting.co.za>
In-reply-to

Content
This issue looks to be a duplicate of #21998. handle-mp_unix2.patch looks more to a workaround than a real issue. When I write asyncio code, I prefer to pass explicitly the loop, so get_event_loop() should never be called. IMO the methods of the event loop should detect the fork and handle the fork directly.

This issue looks to be a duplicate of #21998.

handle-mp_unix2.patch looks more to a workaround than a real issue. When I write asyncio code, I prefer to pass explicitly the loop, so get_event_loop() should never be called. IMO the methods of the event loop should detect the fork and handle the fork directly.

History
Date	User	Action	Args
2015-02-04 21:06:34	vstinner	set	recipients: + vstinner, gvanrossum, yselivanov, dan.oreilly
2015-02-04 21:06:34	vstinner	set	messageid: <1423083994.08.0.392740496312.issue22087@psf.upfronthosting.co.za>
2015-02-04 21:06:34	vstinner	link	issue22087 messages
2015-02-04 21:06:33	vstinner	create