Please skip this question. I had found the reason! It's the mlogging bug! ------------------ Original ------------------ From: "KaShining";<mail2shine@qq.com>; Date: Tue, Dec 24, 2013 05:00 PM To: "pypy-dev"<pypy-dev@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@qq.com>; Date: Tue, Dec 24, 2013 04:15 PM To: "pypy-dev"<pypy-dev@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