Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #46590 > unrolled thread
| Started by | Peter Otten <__peter__@web.de> |
|---|---|
| First post | 2013-05-31 11:55 +0200 |
| Last post | 2013-05-31 11:55 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Surprising difference between StringIO.StringIO and io.StringIO Peter Otten <__peter__@web.de> - 2013-05-31 11:55 +0200
| From | Peter Otten <__peter__@web.de> |
|---|---|
| Date | 2013-05-31 11:55 +0200 |
| Subject | Re: Surprising difference between StringIO.StringIO and io.StringIO |
| Message-ID | <mailman.2482.1369994407.3114.python-list@python.org> |
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. > replacement for StringIO.StringIO/cStringIO.StringIO if you need a > binary stream.
Back to top | Article view | comp.lang.python
csiph-web