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 rcronk
Recipients lowell87, mramahi77, neyro, rcronk, vinay.sajip
Date 2009-05-22.17:45:33
SpamBayes Score 7.21389e-05
Marked as misclassified No
Message-id <1243014335.81.0.514826846564.issue4749@psf.upfronthosting.co.za>
In-reply-to
Content
I have had this problem with 2.6.1 on windows from multiple _threads_ 
instead of multiple processes.  Is that not supported either?  If not, 
what is the workaround for logging from multiple threads?  Shouldn't it 
be easy to use a semaphore within the logging code to make it thread 
safe at least?  I have had this problem on multiple PC's with multiple 
versions of python, and multiple versions of windows.
History
Date User Action Args
2009-05-22 17:45:36rcronksetrecipients: + rcronk, vinay.sajip, mramahi77, lowell87, neyro
2009-05-22 17:45:35rcronksetmessageid: <1243014335.81.0.514826846564.issue4749@psf.upfronthosting.co.za>
2009-05-22 17:45:33rcronklinkissue4749 messages
2009-05-22 17:45:33rcronkcreate