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 Mariatta, Winterflower, eric.araujo, gvanrossum, vstinner, yselivanov
Date 2016-10-22.07:05:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYaoVMC1s41YJoyxpKGEKpOCcHGojVcdv4d1zFEFHhywQ@mail.gmail.com>
In-reply-to <1477114038.63.0.583450338913.issue20847@psf.upfronthosting.co.za>
Content
+Logs for :mod:`asyncio` module should always point to a file on the local
+filesystem.  Using any kind of network logging will block the event loop.

Well... even writing to a local file can block :-/

By "network", what about the local UNIX socket used by syslog?

I guess that the safest option would be a new asyncio library running
all logs functions to a thread, or maybe using loop.run_in_executor().
History
Date User Action Args
2016-10-22 07:05:47vstinnersetrecipients: + vstinner, gvanrossum, eric.araujo, yselivanov, Winterflower, Mariatta
2016-10-22 07:05:47vstinnerlinkissue20847 messages
2016-10-22 07:05:47vstinnercreate