Message89049
| Author |
Frans |
| Recipients |
Frans, lowell87, mramahi77, neyro, rcronk, vinay.sajip |
| Date |
2009年06月07日.19:11:59 |
| SpamBayes Score |
1.8529985e-06 |
| Marked as misclassified |
No |
| Message-id |
<33db10b30906071211v72eddfe1iad96ba2ccece97cc@mail.gmail.com> |
| In-reply-to |
<1244374518.42.0.410109776405.issue4749@psf.upfronthosting.co.za> |
| Content |
Hi Vinay,
Thanks for your info. I have just shared my experience. I ran into a problem
(apperently, there is one) and found a work-around that fits my needs.
If I find the real fix, I will surely follow up on it.
Regards,
Frans
2009年6月7日 Vinay Sajip <report@bugs.python.org>
>
> Vinay Sajip <vinay_sajip@yahoo.co.uk> added the comment:
>
> ConcurrentLogHandler is for multiple *processes* writing to the same
> file, not multiple threads in a single process. Python logging does not
> support multiple processes writing to the same file because there is no
> portable IPC locking across all platforms supported by Python.
> ConcurrentLogHandler uses portalocker to achieve interprocess
> synchronization, and there is no equivalent mechanism which is part of
> the Python stdlib. AFAIK portalocker works on Windows and Linux - I'm
> not sure about other platforms.
>
> Python logging *does* support multiple threads in a single process
> writing to the same file, which is why I asked Robert if it was
> definitely a single-process environment he was working in.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue4749>
> _______________________________________
> |
| Files |
| File name |
Uploaded |
|
unnamed
|
Frans,
2009年06月07日.19:11:59
|
|