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 Frans
Recipients Frans, lowell87, mramahi77, neyro, rcronk, vinay.sajip
Date 2009-06-07.19:11:59
SpamBayes Score 1.853e-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
History
Date User Action Args
2009-06-07 19:12:01Franssetrecipients: + Frans, vinay.sajip, mramahi77, lowell87, neyro, rcronk
2009-06-07 19:12:00Franslinkissue4749 messages
2009-06-07 19:12:00Franscreate