Futurize maps StringIO.StringIO to io.StringIO

[Skip Montanaro]

Thanks. In one instance I used six.StringIO, which seems to work. The
question I had was more why futurize makes a transformation which is an
obvious semantic change.

Skip

On Thu, Mar 8, 2018, 7:55 PM Mark Lawrence <breamoreboy at gmail.com> wrote:

> On 08/03/18 02:34, Skip Montanaro wrote:
> > I had some deja vu recently, cuz of this old thread:
> >
> > https://mail.python.org/pipermail/python-list/2013-May/648245.html
> >
> > Today the context is different, but the problem remains the same. One
> > of the futurize refactoring tools converts usage of StringIO.StringIO
> > to io.StringIO, which, given that the latter accepts just about
> > anything you through at it, is a bit surprising. Perhaps there is no
> > true corresponding class in the io module?
> >
> > Skip
> >
>
> Maybe you need io.BytesIO?
>
> --
> My fellow Pythonistas, ask not what our language can do for you, ask
> what you can do for our language.
>
> Mark Lawrence
>
> --
> https://mail.python.org/mailman/listinfo/python-list
>