A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-June/100567.html below:

[Python-Dev] Reintroduce or drop completly hex, bz2, rot13, ... codecs

[Python-Dev] Reintroduce or drop completly hex, bz2, rot13, ... codecsTerry Reedy tjreedy at udel.edu
Thu Jun 10 21:31:58 CEST 2010
On 6/10/2010 7:08 AM, M.-A. Lemburg wrote:
> Walter Dörwald wrote:

>>> The PEP would also serve as a reference back to both this discussion and
>>> the previous one (which was long enough ago that I've forgotten most of it).
>>
>> I too think that a PEP is required here.
>
> Fair enough. I'll write a PEP.

Thank you from me.
>
>> Codecs support several types of error handling that don't make sense for
>> transform()/untransform(). What should 'abc'.decode('hex', 'replace')
>> do? (In 2.6 it raises an assertion error, because errors *must* be strict).

I would expext either ValueError: errors arg must be 'strict' for 
trransform or else TypeError: tranform takes 1 arg, 2 given.

> That's not really an issue since codecs don't have to implement
> all error handling schemes.
>
> For starters, they will all only implement 'strict' mode.

Terry Jan Reedy


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4