Futurize maps StringIO.StringIO to io.StringIO
On 08/03/18 02:34, Skip Montanaro wrote:
> I had some deja vu recently, cuz of this old thread:
> 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?
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.