[Python-Dev] 'warnings' module changes still breaking Twisted, still looking for a fix (original) (raw)
glyph at divmod.com glyph at divmod.com
Fri Sep 5 00:46:41 CEST 2008
- Previous message: [Python-Dev] 'warnings' module changes still breaking Twisted, still looking for a fix
- Next message: [Python-Dev] 'warnings' module changes still breaking Twisted, still looking for a fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10:35 pm, brett at python.org wrote:
It is not hard to force an import of warnings to use the pure Python version and totally ignore the C implementation. See testwarnings on how to pull that off. Then you can do your hack of overriding warnexplicit().
Benjamin Peterson's recommendation sounds like the winner (since we need to do something different in 2.6 anyway). Forcing the import leads to a bunch of import-ordering problems, since the testing tool itself wants to emit warnings, and self-test, and then it has to import the module and set an attribute on the SUT module...
Thanks for the tip, though.
- Previous message: [Python-Dev] 'warnings' module changes still breaking Twisted, still looking for a fix
- Next message: [Python-Dev] 'warnings' module changes still breaking Twisted, still looking for a fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]