Message89265
| Author |
vinay.sajip |
| Recipients |
Frans, lowell87, mramahi77, neyro, rcronk, vinay.sajip |
| Date |
2009年06月11日.22:47:07 |
| SpamBayes Score |
1.3670694e-07 |
| Marked as misclassified |
No |
| Message-id |
<1244760429.28.0.714578919173.issue4749@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Lowell, there's a working sample right there in the docs:
I mentioned it in msg78619 in this issue. The link is
http://docs.python.org/library/logging.html#sending-and-receiving-logging-events-across-a-network
This should get anyone started for a multiprocess logging requirement.
For a single-process multi-threaded scenario, Python logging should work
out of the box except in scenarios already discussed, where child
processes contend for the files - as per thredio.py - and if one can't
avoid spawning child processes which cause contention, then the socket
logging approach with a separate process can be used. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年06月11日 22:47:09 | vinay.sajip | set | recipients:
+ vinay.sajip, mramahi77, lowell87, neyro, rcronk, Frans |
| 2009年06月11日 22:47:09 | vinay.sajip | set | messageid: <1244760429.28.0.714578919173.issue4749@psf.upfronthosting.co.za> |
| 2009年06月11日 22:47:07 | vinay.sajip | link | issue4749 messages |
| 2009年06月11日 22:47:07 | vinay.sajip | create |
|