Skip to content

Commit ed7e0cc

Browse files
committed
Update changelog. Fixes #105 and Fixes #113.
--HG-- extra : amend_source : 10cadb252bc504ef25c9f9cf7f3cdc5bf03fd367
1 parent e9926a4 commit ed7e0cc

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

CHANGES.txt

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,29 @@ CHANGES
99
* Issue #114: Use ``sys.getfilesystemencoding`` for decoding config in
1010
``bdist_wininst`` distributions.
1111

12+
* Issue #105 and Issue #113: Establish a more robust technique for
13+
determining the terminal encoding::
14+
15+
1. Try ``getpreferredencoding``
16+
2. If that returns US_ASCII or None, try the encoding from
17+
``getdefaultlocale``. If that encoding was a "fallback" because Python
18+
could not figure it out from the environment or OS, encoding remains
19+
unresolved.
20+
3. If the encoding is resolved, then make sure Python actually implements
21+
the encoding.
22+
4. On the event of an error or unknown codec, revert to fallbacks
23+
(UTF-8 on Darwin, ASCII on everything else).
24+
5. On the encoding is 'mac-roman' on Darwin, use UTF-8 as 'mac-roman' was
25+
a bug on older Python releases.
26+
27+
On a side note, it would seem that the encoding only matters for when SVN
28+
does not yet support ``--xml`` and when getting repository and svn version
29+
numbers. The ``--xml`` technique should yield UTF-8 according to some
30+
messages on the SVN mailing lists. So if the version numbers are always
31+
7-bit ASCII clean, it may be best to only support the file parsing methods
32+
for legacy SVN releases and support for SVN without the subprocess command
33+
would simple go away as support for the older SVNs does.
34+
1235
---
1336
1.4
1437
---

0 commit comments

Comments
 (0)