[pypy-dev] why logging in pypy not need acquire lock?

[KaShining]

Please skip this question.

I had found the reason!
It's the mlogging bug!




------------------ Original ------------------
From:  "KaShining";<mail2shine at qq.com>;
Date:  Tue, Dec 24, 2013 05:00 PM
To:  "pypy-dev"<pypy-dev at python.org>; 

Subject:  Re:why logging in pypy not need acquire lock?



I take this question because I use the mlogging under pypy have something wrong like that:
[10458] 4127 eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
[10464] 426 eeeeeeeeeeeeeeeeee[10461] 1670 iiiiiiiiiiiiiiii

the right log should be:

[10458] 4127 eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
[10464] 426 eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
[10461] 1670 iiiiiiiiiiiiiiii

about mlogging https://pypi.python.org/pypi/mlogging



------------------ Original ------------------
From:  "KaShining";<mail2shine at qq.com>;
Date:  Tue, Dec 24, 2013 04:15 PM
To:  "pypy-dev"<pypy-dev at python.org>; 

Subject:  why logging in pypy not need acquire lock?





why logging in pypy not need acquire lock?
left from pypy whle right from cpython
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20131224/d5adef6d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6D8CA44F at CF570723.7255B952.jpg
Type: image/jpeg
Size: 266338 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20131224/d5adef6d/attachment-0001.jpg>