[issue3618] possible deadlock in python IO implementation

Benjamin Peterson added the comment: I suppose we might as well. If anyone wants to fix the Python implementation later, they can go ahead and reopen this. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue3618] possible deadlock in python IO implementation

STINNER Victor added the comment: Ooops, I wanted to write: "Why not *closing* this issue?", sorry. ___ Python tracker ___ ___ Python-bugs-list

[issue3618] possible deadlock in python IO implementation

Benjamin Peterson added the comment: 2009/3/4 STINNER Victor : > > STINNER Victor added the comment: > >> Since io-c has been merging, I'm lowering priority. > > Why not fixing this issue? The issue is rare (only occurs when using profiling > with a callback writting to stdout) and you closed t

[issue3618] possible deadlock in python IO implementation

STINNER Victor added the comment: > Since io-c has been merging, I'm lowering priority. Why not fixing this issue? The issue is rare (only occurs when using profiling with a callback writting to stdout) and you closed the issue #4862 which is more common (read an UTF-16 file). __

[issue3618] possible deadlock in python IO implementation

Benjamin Peterson added the comment: Since io-c has been merging, I'm lowering priority. -- priority: critical -> low title: possible deadlock in IO library (Lib/io.py) -> possible deadlock in python IO implementation ___ Python tracker