Marc-Andre Lemburg <m...@egenix.com> added the comment:
lplatypus wrote:
>
> lplatypus <l...@deller.id.au> added the comment:
>
> Okay thanks, but in that case might I suggest that this limitation be
> mentioned in the documentation for sys.setdefaultencoding? It currently
> reads as if any available encoding is acceptable. Perhaps even a warning or
> exception should be produced when calling it wrongly?
>
> Other places that may need review include:
> - the programming FAQ on python.org which presents the option of calling
> setdefaultencoding('mbcs') on windows (
> http://www.python.org/doc/faq/programming/#what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean
> )
> - the comments in site.py which provoke changing the default encoding
> - PEP100 which suggests enabling this code in site.py
>
> BTW would patches ever be considered to fix issues such as this with using
> other encodings as default encodings, or is there some objection to the
> concept?
No, Python 2.x's Unicode implementation only supports ASCII as default
encoding. In Python 3.x, UTF-8 is used as default encoding.
Note that this limitation only affects cases where you mix string
and Unicode objects used as keys in a dictionary. If you avoid
this situation, there are no dictionary problems with using
different default encoding. However, you may run into other problems.
----------
nosy: +lemburg
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue7890>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
