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

2016-11-02 Thread Mariatta Wijaya 

Changes by Mariatta Wijaya :


Removed file: http://bugs.python.org/file45182/issue20847.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2016-10-25 Thread Guido van Rossum 

Changes by Guido van Rossum :


--
nosy:  -gvanrossum

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2016-10-25 Thread Марк Коренберг 

Марк Коренберг added the comment:

Typical network logging is using syslog UDP. Sending UDP is never block.

--
nosy: +mmarkk

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2016-10-22 Thread STINNER Victor 

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 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().

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2016-10-21 Thread Mariatta Wijaya 

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2016-05-18 Thread Camilla Montonen 

Changes by Camilla Montonen :


--
nosy: +Winterflower

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-06-06 Thread STINNER Victor 

Changes by STINNER Victor victor.stin...@gmail.com:


--
components: +Asyncio

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-05-09 Thread Ezio Melotti 

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-03-07 Thread Éric Araujo 

Changes by Éric Araujo mer...@netwok.org:


--
nosy: +eric.araujo

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-03-03 Thread Guido van Rossum 

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: 212664
nosy: gvanrossum, haypo
priority: normal
severity: normal
status: open
title: asyncio docs should call out that network logging is a no-no
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-03-03 Thread Yury Selivanov 

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 really matter how logging is configured.

--
nosy: +yselivanov

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-03-03 Thread Guido van Rossum 

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. :-)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

2014-03-03 Thread Yury Selivanov 

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 misconfigure. Having [logger+queue+logging 
thread] combination mitigates the risk a bit, but yeah, at the cost of 
increased complexity...

 Anyway, in 3.4 it is what it is. :-)

Right.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20847
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com