Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #46593
| From | Serhiy Storchaka <storchaka@gmail.com> |
|---|---|
| Subject | Re: Surprising difference between StringIO.StringIO and io.StringIO |
| Date | 2013-05-31 13:35 +0300 |
| References | <CANc-5UyDZ=ArzKrs=Y9CDwNwOunDt3DGpy5KKATZ_R=Z-LsHtA@mail.gmail.com> <ko9r4m$a1c$1@ger.gmane.org> <ko9s26$imp$2@ger.gmane.org> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2486.1369996552.3114.python-list@python.org> (permalink) |
31.05.13 12:55, Peter Otten написав(ла): > Serhiy Storchaka wrote: > >> 30.05.13 23:46, Skip Montanaro написав(ла): >>> Am I missing something about how io.StringIO works? I thought it was >>> a more-or-less drop-in replacement for StringIO.StringIO. >> >> io.StringIO was backported from Python 3. It is a text (unicode) stream. >> cStringIO.StringIO is a binary stream and StringIO.StringIO can be used >> as binary or unicode stream depending on arguments. Use io.BaseIO as a > > I think you mean io.BytesIO. Indead, thank you for correction. >> replacement for StringIO.StringIO/cStringIO.StringIO if you need a >> binary stream. > >
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Surprising difference between StringIO.StringIO and io.StringIO Serhiy Storchaka <storchaka@gmail.com> - 2013-05-31 13:35 +0300
csiph-web