[issue6030] io.BufferedWriter C module missing _write_lock

Antoine Pitrou added the comment: The C BufferedWriter class itself is thread-safe. I'm not sure what you are worried about, perhaps you are writing your own derived class? -- nosy: +pitrou ___ Python tracker _

[issue6030] io.BufferedWriter C module missing _write_lock

Josh Roesslein added the comment: Okay so even if you extend the BufferedWriter class, you should not be using that lock for thread safety, correct? But you must still use locks since its not thread safe still? -- ___ Python tracker

[issue6030] io.BufferedWriter C module missing _write_lock

Benjamin Peterson added the comment: That's supposed to be a private attribute, so, yes, the omission was purposeful. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker __

[issue6030] io.BufferedWriter C module missing _write_lock

New submission from Josh Roesslein : The C version of BufferedWriter is missing the _write_lock attribute. I am not sure if there is a reason for this or it was left out by accident. Python version still has the attribute. -- components: Extension Modules, IO, Library (Lib) messages: 878