RetroSearch Browse

Mon Aug 6 20:24:15 CEST 2007 · https://mail.python.org/pipermail/python-dev/2007-August/074105.html

Oops, never mind. This was in the context of 2.5 and 2.6, but my reply
was in the context of 3.0. Still, in the light of cStringIO
disappearing, it would be good to keep cStringIO is stable as possible
(probably restoring 2.5.0 behavior) so as to avoid breaking 3rd party
code more than once.

On 8/6/07, Guido van Rossum <guido at python.org> wrote:
> On 8/6/07, Georg Brandl <g.brandl at gmx.net> wrote:
> > Guido van Rossum schrieb:
> > > Methinks that this was a fundamental limitation of cStringIO, not  a
> > > bug. Certainly not something to be "fixed" in a bugfix release.
> >
> > I'm sorry.
>
> No problem. Somebody else should have flagged this, so it's our
> collective responsibility.
>
> > Okay, I propose the following patch:
> >
> > Index: Modules/cStringIO.c
> [...]
>
> My proposal is much more radical -- get rid of cStringIO altogether.
> (And also of StringIO.py.) There aren't that many places using it any
> more, and almost all of these are easily replaced with io.StringIO (or
> io.BytesIO!). There's already a fixer in 2to3 to do this.
>
> --
> --Guido van Rossum (home page: http://www.python.org/~guido/)
>

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2007-August/074105.html below:

[Python-Dev] cStringIO.StringIO() buffer behavior