STINNER Victor victor.stin...@haypocalc.com added the comment:
This feature was requested only once, 4 years ago, so I don't think that the
feature is a must-have :-)
I think that a lot of code have to be modified in Python parser to support
UTF-16-* and UTF-32-* codecs. Since there is no
Georg Brandl ge...@python.org added the comment:
Why am I assigned this issue?
--
assignee: georg.brandl -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1503789
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Attached patch is a partial fix: support UTF-16-LE, UTF-16-BE and
UTF-32-LE. Some remarks about my patch:
* UTF-32-BE is not supported because I'm too lazy tonigh
to finish the patch and because such file begins with 0x00 0x00
STINNER Victor victor.stin...@haypocalc.com added the comment:
Detect UTF-16 and UTF-32 is complex. I think that we can first support
UTF-16LE, UTF-16BE, UTF-32LE and UTF-32BE with BOM. Most editors add a
BOM (eg. notepad.exe on Windows). I will try to fix this issue.
--
Changes by Daniel Diniz aja...@gmail.com:
--
assignee: - georg.brandl
components: +Unicode
nosy: +georg.brandl, haypo
stage: - test needed
versions: +Python 2.7, Python 3.1 -Python 2.6
___
Python tracker rep...@bugs.python.org
Christian Heimes added the comment:
I turned it into a feature request for 2.6 with low priority. Somebody
should either fix/implement the UTF-16 support or update the docs.
--
components: +Documentation
nosy: +tiran
priority: normal - low
type: - rfe
versions: +Python 2.6 -Python 2.4
