Merge lp:~vila/bzr/625686-selftest-cleanup-deprecation-warnings into lp:bzr
Status: | Merged |
---|---|
Approved by: | Vincent Ladeuil |
Approved revision: | no longer in the source branch. |
Merged at revision: | 5399 |
Proposed branch: | lp:~vila/bzr/625686-selftest-cleanup-deprecation-warnings |
Merge into: | lp:bzr |
Diff against target: |
139 lines (+40/-16) 4 files modified
NEWS (+3/-0) bzrlib/builtins.py (+8/-4) bzrlib/symbol_versioning.py (+29/-11) bzrlib/versionedfile.py (+0/-1) |
To merge this branch: | bzr merge lp:~vila/bzr/625686-selftest-cleanup-deprecation-warnings |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman (community) | Approve | ||
Review via email:
|
Commit message
Cleanup warnings.filters after running selftest
Description of the change
This fixes bug #625686 by cleaning up the warning filter added by cmd_selftest.
See bug description for details but roughly, cmd_selftest wasn't properly isolated.
This is the least intrusive patch, but we may want to revisit either
blackbox/
or re-think the way we play with warnings.
so it may be overkill though).
Finally, having re-read symbol_
function there start with 'deprecated'. How about renaming the module
itself to deprecated ?
So instead of writing 'symbol_
the simpler 'deprecated.in()' and so on ?
I'm not sure about how to deprecate the 'symbol_versioning' module itself
in that case though ;)
On the other hand, I'm not sure many plugins depend on it either, thoughts ?
Change looks good to me. One thing, I'd prefer if you passed and closed over the warnings.filters list as well as well as the tuple just added, to defend against that module global changing.
The warnings module upsets me a little more every time I go near it...