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

2010-06-10 Thread Stephen J. Turnbull
Antoine Pitrou writes: > In which cases is this true? Hex is rarely used for ASCII-encoding of > binary data, precisely because its efficiency is poor. MIME quoted-printable, URL-quoting, and XBM come to mind. ___ Python-Dev mailing list Python-Dev@p

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

2010-06-10 Thread Baptiste Carvello
Victor Stinner a écrit : I suppose that each codec will have a different list of accepted input and output types. Example: bz2: encode:bytes->bytes, decode:bytes->bytes rot13: encode:str->str, decode:str->str hex: encode:bytes->str, decode: str->bytes A user point of view: please

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

2010-06-10 Thread Walter Dörwald
On 09.06.10 14:47, Nick Coghlan wrote: > On 09/06/10 22:18, Victor Stinner wrote: >> Le mercredi 09 juin 2010 10:41:29, M.-A. Lemburg a écrit : >>> No, .transform() and .untransform() will be interface to same-type >>> codecs, i.e. ones that convert bytes to bytes or str to str. As with >>> .encod

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

2010-06-10 Thread M.-A. Lemburg
Walter Dörwald wrote: > On 09.06.10 14:47, Nick Coghlan wrote: > >> On 09/06/10 22:18, Victor Stinner wrote: >>> Le mercredi 09 juin 2010 10:41:29, M.-A. Lemburg a écrit : No, .transform() and .untransform() will be interface to same-type codecs, i.e. ones that convert bytes to bytes or

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

2010-06-10 Thread Victor Stinner
Le jeudi 10 juin 2010 12:30:01, Walter Dörwald a écrit : > Codecs support several types of error handling that don't make sense for > transform()/untransform(). What should 'abc'.decode('hex', 'replace') > do? You mean 'abc'.transform('hex', 'replace'), right? Error handler is useful for encoding

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

2010-06-10 Thread R. David Murray
On Thu, 10 Jun 2010 12:27:33 +0200, Baptiste Carvello wrote: > Victor Stinner wrote: > > > I suppose that each codec will have a different list of accepted input and > > output types. Example: > > >bz2: encode:bytes->bytes, decode:bytes->bytes > >rot13: encode:str->str, decode:str->str

Re: [Python-Dev] Future of 2.x.

2010-06-10 Thread Barry Warsaw
On Jun 10, 2010, at 09:01 AM, Steve Holden wrote: >The current stumbling block isn't the language itself, it's the lack of >support from third-party libraries. GSoC is addressing some of these >issues, but so far we (the PSF, the dev community, anybody else except >R. David Murray) haven't really

Re: [Python-Dev] Future of 2.x.

2010-06-10 Thread Terry Reedy
On 6/10/2010 2:48 AM, Senthil Kumaran wrote: On Thu, Jun 10, 2010 at 6:40 AM, Alexandre Vassalotti wrote: On Wed, Jun 9, 2010 at 1:23 PM, "Martin v. Löwis" wrote: Closing the backport requests is fine. For the feature requests, I'd only close them *after* the 2.7 release (after determining t

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

2010-06-10 Thread Terry Reedy
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. T