➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2009-05-15 20:25 by jroesslein, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg87831 - (view) | Author: Josh Roesslein (jroesslein) | Date: 2009-05-15 20:25 | |
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. |
|||
| msg87832 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2009-05-15 20:27 | |
That's supposed to be a private attribute, so, yes, the omission was purposeful. |
|||
| msg87835 - (view) | Author: Josh Roesslein (jroesslein) | Date: 2009-05-15 20:38 | |
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? |
|||
| msg87837 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2009-05-15 20:41 | |
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? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:48 | admin | set | github: 50280 |
| 2009-05-15 20:41:19 | pitrou | set | nosy:
+ pitrou messages: + msg87837 |
| 2009-05-15 20:38:56 | jroesslein | set | messages: + msg87835 |
| 2009-05-15 20:27:54 | benjamin.peterson | set | status: open -> closed nosy: + benjamin.peterson messages: + msg87832 resolution: not a bug |
| 2009-05-15 20:25:02 | jroesslein | create | |