Typo in cStringIO

[jmfauth]

BPO	8121
Nosy	@birkenfeld

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-03-12.10:18:42.875>
created_at = <Date 2010-03-12.10:14:44.645>
labels = ['type-bug', 'invalid']
title = 'Typo in cStringIO'
updated_at = <Date 2010-03-12.11:00:20.649>
user = 'https://bugs.python.org/jmfauth'

bugs.python.org fields:

activity = <Date 2010-03-12.11:00:20.649>
actor = 'jmfauth'
assignee = 'none'
closed = True
closed_date = <Date 2010-03-12.10:18:42.875>
closer = 'georg.brandl'
components = ['None']
creation = <Date 2010-03-12.10:14:44.645>
creator = 'jmfauth'
dependencies = []
files = []
hgrepos = []
issue_num = 8121
keywords = []
message_count = 3.0
messages = ['100920', '100921', '100927']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'jmfauth']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue8121'
versions = ['Python 2.6']

[jmfauth]

There is a malformed string in the module cStringIO.

StringI <--> StringIO

>>> sys.version
2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit (Intel)]
>>> StringIO.StringIO('123')
<StringIO.StringIO instance at 0x02D230D0>
>>> cStringIO.StringIO('123')
<cStringIO.StringI object at 0x0183ECB0>
>>>

[birkenfeld]

That name is actually correct. cStringIO features two different types, depending on whether you call cStringIO.StringIO() with or without an argument. One is called "StringI", the other "StringO".

[jmfauth]

Wow! I never been aware of this (documentation, dir(), __doc__)
Indeed:

>>> cStringIO.StringIO()
<cStringIO.StringO object at 0x02D94F40>
>>> cStringIO.StringIO('abc')
<cStringIO.StringI object at 0x016DE920>

Sorry for the noise.