|
|
|
Tell HN: Python's print function is thread-unsafe
|
|
13 points
by kerneloops
904 days ago
|
|
Some days ago I found that Python's print function is by default thread-unsafe, as the underlying sys.stdout is by default a TextIOWrapper, which is not thread safe. That means, for the code below from threading import Thread
def target(x):
for _ in range(100000): print(x)
Thread(target=target, args=['a' * 10]).start()
Thread(target=target, args=['b' * 10]).start()
Python could print out not only interleaved bytes (aaabbbabab), but also null bytes and uninitialized memory, thanks to non-synchronized buffering. |
|
C printf: MT-Safe locale.
C++ std::cout: safe, unless you call sync_with_stdio(false).
JVM System.out.println: safe in common JVMs.
C# Console.WriteLine: safe.
Go fmt.Printf: safe.
Rust println!: safe.
Ruby puts: safe.
So it seems that Python is the outlier here.