Merge lp://staging/~jameinel/bzr/2.0.2-deprecation-warnings-440062 into lp://staging/bzr/2.0
Proposed by
John A Meinel
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp://staging/~jameinel/bzr/2.0.2-deprecation-warnings-440062 |
Merge into: | lp://staging/bzr/2.0 |
Diff against target: |
26 lines 2 files modified
NEWS (+3/-0) bzrlib/commands.py (+1/-1) |
To merge this branch: | bzr merge lp://staging/~jameinel/bzr/2.0.2-deprecation-warnings-440062 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
bzr-core | Pending | ||
Review via email: mp+13293@code.staging.launchpad.net |
To post a comment you must log in.
Python 2.6 now 'comes with' a deprecation warning suppression as part of
the threading module. So the current check that says 'if someone manually
configured a deprecation warning filter, don't add ours' now breaks
because there is always one present.
So instead, we just always suppress all deprecation warnings if we are in
a 'final' release.
Whether this lands in 2.0.1 or 2.0.2 just depends on how quickly it gets reviewed versus how long it takes the admins to create a 2.0.1 branch for me. :)