Fixes #1730114.

arguments (even for -1). Fixes the last bit of
#1359365.

arguments with the system default encoding just like the write()
method does, instead of converting it to a raw buffer.

now if close() has been called before (like file and StringIO.StringIO do)

after calling close(). Change StringIO, so that it behaves the same way.

returns in cStringIO.c.  Thanks to Andrew Bennetts.

This must be a backport candidate.

Add function names to various PyArg_ParseTuple calls in bz2module.c.

truncate() left the stream position unchanged, which meant the
"truncated" data didn't go away:

>>> io.write('abc')
>>> io.truncate(0)
>>> io.write('xyz')
>>> io.getvalue()
'abcxyz'

Patch by Dima Dorfman.

and test_support.run_classtests() into run_unittest()
and use it wherever possible.

Also don't use "from test.test_support import ...", but
"from test import test_support" in a few spots.

From SF patch #662807.

(requested by GvR. patch contributed by Michael Stone)

imports e.g. test_support must do so using an absolute package name
such as "import test.test_support" or "from test import test_support".

This also updates the README in Lib/test, and gets rid of the
duplicate data dirctory in Lib/test/data (replaced by
Lib/email/test/data).

Now Tim and Jack can have at it. :)

Unicode string snippets to larger Unicode strings.

This fix should also go into Python 2.2.1.

This closes patch "[ #490850 ] Jython and test_StringIO".

iterator, just test to make sure it has the two required iterator
protocol methods __iter__() and next() -- actually just test
hasattr-ness.

input to .write() too.

Lib/test/output/test_StringIO is no longer necessary.

Also, added a test of the iterator protocol that's just been added to
StringIO's and cStringIO's.

string.letters was much more than expected.

Solution: explicit is better than implicit; don't rely on
string.letters.

Added missing clode to make the clode test test a close. ;)

cStringIO does not get it right (reported as SF bug #115531).

Added test for ValueError when write() is called on a closed StringIO
object.  Commented out because cStringIO does not get it right
(reported as SF bug #115530).