[issue20847] asyncio docs should call out that network logging is a no-no

Changes by Mariatta Wijaya : Removed file: http://bugs.python.org/file45182/issue20847.patch ___ Python tracker ___

[issue20847] asyncio docs should call out that network logging is a no-no

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue20847] asyncio docs should call out that network logging is a no-no

Марк Коренберг added the comment: Typical network logging is using syslog UDP. Sending UDP is never block. -- nosy: +mmarkk ___ Python tracker ___

[issue20847] asyncio docs should call out that network logging is a no-no

STINNER Victor added the comment: +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

[issue20847] asyncio docs should call out that network logging is a no-no

Mariatta Wijaya added the comment: Hi, I added to asyncio logging doc that the log file should point to a file on local filesystem. Please review. Thanks :) -- keywords: +patch nosy: +Mariatta Added file: http://bugs.python.org/file45182/issue20847.patch

[issue20847] asyncio docs should call out that network logging is a no-no

Changes by Camilla Montonen : -- nosy: +Winterflower ___ Python tracker ___ ___

[issue20847] asyncio docs should call out that network logging is a no-no

Changes by STINNER Victor victor.stin...@gmail.com: -- components: +Asyncio ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20847 ___ ___

[issue20847] asyncio docs should call out that network logging is a no-no

Changes by Ezio Melotti ezio.melo...@gmail.com: -- components: +Documentation stage: - needs patch type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20847 ___

[issue20847] asyncio docs should call out that network logging is a no-no

Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20847 ___ ___ Python-bugs-list

[issue20847] asyncio docs should call out that network logging is a no-no

New submission from Guido van Rossum: The asyncio package uses the logging module. We should remind users that they should always configure their logs to go to a file on the local filesystem -- using any kind of network logging will block the event loop. -- assignee: haypo messages:

[issue20847] asyncio docs should call out that network logging is a no-no

Yury Selivanov added the comment: Can we instead re-engineer asyncio logging to have logger calls in a separate thread? I.e. `logger` is a proxy object, that puts logging calls in a queue, and there would be another thread to block on the queue and do the actual logging. This way it won't

[issue20847] asyncio docs should call out that network logging is a no-no

Guido van Rossum added the comment: If you really need network logging you should be able to configure a handler that puts things in a queue whose other end is serviced by an asyncio task. There should be no need to mess with the type of the logger object. Anyway, in 3.4 it is what it is. :-)

[issue20847] asyncio docs should call out that network logging is a no-no

Yury Selivanov added the comment: If you really need network logging you should be able to configure a handler that puts things in a queue whose other end is serviced by an asyncio task. There should be no need to mess with the type of the logger object. It's something that is easy to