diff options
author | Charles Harris <charlesr.harris@gmail.com> | 2015-03-14 22:22:32 -0400 |
---|---|---|
committer | Charles Harris <charlesr.harris@gmail.com> | 2015-03-14 22:22:32 -0400 |
commit | c60f1c6d944b25c5a001cf80e9b65dd5d44ed85d (patch) | |
tree | 2d986ac227e6c2b11494753014128db9b50961ef /doc | |
parent | 19d861edd87e0c69aeba5cb5a7d6671518d840a3 (diff) | |
parent | 4c9e5bd362643aadfc027184682c067aa2f10cda (diff) | |
download | numpy-c60f1c6d944b25c5a001cf80e9b65dd5d44ed85d.tar.gz |
Merge pull request #5682 from matthew-brett/add-clear-catch-warnings-cm
MRG: new clear_catch_warnings context manager
Diffstat (limited to 'doc')
-rw-r--r-- | doc/release/1.10.0-notes.rst | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/release/1.10.0-notes.rst b/doc/release/1.10.0-notes.rst index c38a2ae64..d4aaec878 100644 --- a/doc/release/1.10.0-notes.rst +++ b/doc/release/1.10.0-notes.rst @@ -110,6 +110,18 @@ numpy's broadcasting rules. The functionality is similar to broadcast_arrays, which in fact has been rewritten to use broadcast_to internally, but only a single array is necessary. +New context manager *clear_and_catch_warnings* for testing warnings +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +When Python emits a warning, it records that this warning has been emitted in +the module that caused the warning, in a module attribute +``__warningregistry__``. Once this has happened, it is not possible to emit +the warning again, unless you clear the relevant entry in +``__warningregistry__``. This makes is hard and fragile to test warnings, +because if your test comes after another that has already caused the warning, +you will not be able to emit the warning or test it. The context manager +``clear_and_catch_warnings`` clears warnings from the module registry on entry +and resets them on exit, meaning that warnings can be re-raised. + Improvements ============ |