[Python-Dev] Decoder functions accept str in py3k (original) (raw)
M.-A. Lemburg mal at egenix.com
Wed Jan 7 19:57:23 CET 2009
- Previous message: [Python-Dev] Decoder functions accept str in py3k
- Next message: [Python-Dev] Decoder functions accept str in py3k
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2009-01-07 19:32, Antoine Pitrou wrote:
M.-A. Lemburg <mal egenix.com> writes:
No, that's something I explicitly readded to Python 3k, since the codecs interface is independent of the input and output types (the codecs decide which combinations to support). But why would the utf8 decoder accept unicode as input?
It shouldn't.
Looks like the codecs module codec interfaces were not updated to only accept bytes on decode for the Unicode codecs.
BTW: The _codecsmodule.c file is a 4 spaces indent file as well (just like all Unicode support source files). Someone apparently has added tabs when adding support for Py_buffers.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Jan 07 2009)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
- Previous message: [Python-Dev] Decoder functions accept str in py3k
- Next message: [Python-Dev] Decoder functions accept str in py3k
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]