Merge lp:~gz/bzr/unversioned_paths_unprintable_898408 into lp:bzr
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Vincent Ladeuil | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 6346 | ||||
Proposed branch: | lp:~gz/bzr/unversioned_paths_unprintable_898408 | ||||
Merge into: | lp:bzr | ||||
Diff against target: |
147 lines (+57/-5) 5 files modified
bzrlib/tests/blackbox/test_commit.py (+20/-0) bzrlib/tests/per_workingtree/test_paths2ids.py (+11/-0) bzrlib/tests/test_workingtree_4.py (+16/-1) bzrlib/workingtree_4.py (+6/-4) doc/en/release-notes/bzr-2.5.txt (+4/-0) |
||||
To merge this branch: | bzr merge lp:~gz/bzr/unversioned_paths_unprintable_898408 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Vincent Ladeuil | Approve | ||
Review via email: mp+84514@code.launchpad.net |
Commit message
Ensure PathsNotVersion
Description of the change
Make notifying the user that they're trying to operate on unversioned files work without 'Unprintable exception' on utf-8 terminals again.
The problem stems from the fact bzrlib.
There are two reasonable places to re-decode the paths, either in the methods that raise PathsNotVersion
Reporting on non-utf-8 terminals still mangles paths, but that's a long standing issue and this fix moves in the correct direction on that front as well.
Very good explanation in the cover letter really made reviewing this proposal easy. Thanks.
I agree with your analysis and it seems better indeed to leave the exception always deal with unicode paths.