5a77fe92bd
Issue #1548891 : The cStringIO.StringIO() constructor now encodes unicode
...
arguments with the system default encoding just like the write() method
does, instead of converting it to a raw buffer.
2011-10-22 21:26:01 +02:00
f678e82240
Oops, forgot issue number
2011-10-21 22:22:43 +02:00
a5016cd0f7
Add test for fix of issue #1730114 .
2011-10-21 22:22:04 +02:00
4fa68ab10b
raise an ValueError in getvalue() on closed StringIO ( closes #12161 )
...
Thanks for Catalin Iacob for the patch.
2011-05-26 09:56:41 -05:00
0762788081
#7092 - Silence more py3k deprecation warnings, using test_support.check_py3k_warnings() helper.
2010-03-21 01:14:24 +00:00
ce8e33a095
Reverting the Revision: 77368. I committed Flox's big patch for tests by
...
mistake. ( It may come in for sure tough)
2010-01-08 19:04:16 +00:00
3ddc435af6
Fixing - Issue7026 - RuntimeError: dictionary changed size during iteration. Patch by flox
2010-01-08 18:41:40 +00:00
414721614f
make StringIO like other file objects in that readline(-1) has no effect #7348
2009-12-13 17:29:16 +00:00
5c8da86f3a
convert usage of fail* to assert*
2009-06-30 22:57:08 +00:00
9616444427
Revert the fix for #1548891 , it broke backwards compatibility with arbitrary read buffers.
...
Fixes #1730114 .
2007-08-08 13:03:41 +00:00
cffcc8b195
Make cStringIO.truncate raise IOError for negative
...
arguments (even for -1). Fixes the last bit of
#1359365 .
2006-11-19 10:41:41 +00:00
5597e261b2
Bug #1548891 : The cStringIO.StringIO() constructor now encodes unicode
...
arguments with the system default encoding just like the write()
method does, instead of converting it to a raw buffer.
2006-10-12 09:47:12 +00:00
197e8321c6
SF patch #1359365 : cStringIO.StringIO.isatty() will raise a ValueError
...
now if close() has been called before (like file and StringIO.StringIO do)
2006-03-15 22:13:13 +00:00
0af5d93d8a
SF patch #1359365 : file and cStringIO raise a ValueError when next() is called
...
after calling close(). Change StringIO, so that it behaves the same way.
2006-03-15 08:23:53 +00:00
10402a306f
Patches #1298449 and #1298499 : Add some missing checks for error
...
returns in cStringIO.c. Thanks to Andrew Bennetts.
This must be a backport candidate.
2005-09-22 09:19:01 +00:00
bb9c739806
Add error checks for the bz2, cStringIO and operator modules.
...
Add function names to various PyArg_ParseTuple calls in bz2module.c.
2004-11-01 17:10:19 +00:00
037b3ee44e
Patch 1012740: cStringIO's truncate doesn't
...
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.
2004-08-21 06:55:43 +00:00
5475f2394a
SF bug #770485 : cStringIO does not set closed attr
2003-08-08 12:20:03 +00:00
21d3a32b99
Combine the functionality of test_support.run_unittest()
...
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 .
2003-05-01 17:45:56 +00:00
352f9477da
SF patch 695710: fix bug 678519: cStringIO self iterator
...
(requested by GvR. patch contributed by Michael Stone)
2003-04-24 15:50:11 +00:00
04f357cffe
Get rid of relative imports in all unittests. Now anything that
...
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. :)
2002-07-23 19:04:11 +00:00
e1c67d1dc0
Make StringIO work in --disable-unicode builds...
2002-05-13 09:42:16 +00:00
e4418609f7
Whitespace normalization.
2002-02-16 07:34:19 +00:00
f853be980e
Restore Python 2.1 StringIO.py behaviour: support concatenating
...
Unicode string snippets to larger Unicode strings.
This fix should also go into Python 2.2.1.
2002-01-06 17:15:05 +00:00
793ead5696
A workaround for the missing buffer() builtin in jython.
...
This closes patch "[ #490850 ] Jython and test_StringIO".
2001-12-09 20:06:32 +00:00
45653503ec
test_iterator(): Don't do a type comparison to see if it's an
...
iterator, just test to make sure it has the two required iterator
protocol methods __iter__() and next() -- actually just test
hasattr-ness.
2001-09-25 21:40:04 +00:00
e47df7a211
StringIO patch #462596 : let's [c]StringIO accept read buffers on
...
input to .write() too.
2001-09-24 17:34:52 +00:00
7f8ff471f8
Converted test_StringIO.py to use unittest, so
...
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.
2001-09-22 04:33:47 +00:00
cafd495dfe
In O_writelines: Replace use of string.joinfields with "".join.
2001-02-09 23:44:22 +00:00
22d5895dc3
Added a test for the StringIO write() error I just fixed.
2000-10-12 16:46:28 +00:00
4bbea05c4e
Jack Jansen reported that the regression test failed on the Mac where
...
string.letters was much more than expected.
Solution: explicit is better than implicit; don't rely on
string.letters.
2000-10-11 21:34:53 +00:00
d1229f5651
Uncommented tests that failed for cStringIO,
...
Added missing clode to make the clode test test a close. ;)
2000-10-06 19:21:32 +00:00
954383356f
Added some tests for the truncate() method; one is commented out because
...
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 ).
2000-09-28 04:25:33 +00:00
b96e0e5e65
New test cases for the StringIO module
2000-09-19 16:35:39 +00:00
Antoine Pitrou
Benjamin Peterson
Florent Xicluna
Senthil Kumaran
Georg Brandl
Martin v. Löwis
Walter Dörwald
Michael W. Hudson
Tim Peters
Raymond Hettinger
Barry Warsaw
Marc-André Lemburg
Finn Bock
Jeremy Hylton
Guido van Rossum
Jim Fulton
Fred Drake