[issue6647] warnings.catch_warnings is not thread-safe

2010-04-02 Thread A.M. Kuchling
A.M. Kuchling li...@amk.ca added the comment: Added a warning to 2.x trunk in r79607, and Gabriel's doc change in r79608. This thread-unsafety seems specialized and rarely of great importance, so I used the note:: directive, not warning::. -- nosy: +akuchling resolution: - fixed

[issue6647] warnings.catch_warnings is not thread-safe

2009-11-15 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: Document that warnings.catch_warnings is not thread safe. -- keywords: +patch Added file: http://bugs.python.org/file15341/warnings.diff ___ Python tracker rep...@bugs.python.org

[issue6647] warnings.catch_warnings is not thread-safe

2009-08-05 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Any function whose purpose is to mutate global (non thread-local) state is inherently thread-unsafe. The only reasonable possibility is to document it as such. -- assignee: - georg.brandl components: +Documentation nosy: +georg.brandl,

[issue6647] warnings.catch_warnings is not thread-safe

2009-08-04 Thread Gabriel Genellina
New submission from Gabriel Genellina gagsl-...@yahoo.com.ar: warnings.catch_warnings is a context manager supposed to save and restore warnings filters, and optionally record all warnings issued. But it does so in a completely thread-unsafe way, by replacing the module's showwarning and