summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_StringIO.py
Commit message (Collapse)AuthorAgeFilesLines
* Issue #1548891: The cStringIO.StringIO() constructor now encodes unicodeAntoine Pitrou2011-10-221-0/+21
| | | | | arguments with the system default encoding just like the write() method does, instead of converting it to a raw buffer.
* Oops, forgot issue numberAntoine Pitrou2011-10-211-1/+1
|
* Add test for fix of issue #1730114.Antoine Pitrou2011-10-211-0/+8
|
* raise an ValueError in getvalue() on closed StringIO (closes #12161)Benjamin Peterson2011-05-261-0/+4
| | | | Thanks for Catalin Iacob for the patch.
* #7092 - Silence more py3k deprecation warnings, using ↵Florent Xicluna2010-03-211-6/+4
| | | | test_support.check_py3k_warnings() helper.
* Reverting the Revision: 77368. I committed Flox's big patch for tests bySenthil Kumaran2010-01-081-4/+6
| | | | mistake. ( It may come in for sure tough)
* Fixing - Issue7026 - RuntimeError: dictionary changed size during iteration. ↵Senthil Kumaran2010-01-081-6/+4
| | | | Patch by flox
* make StringIO like other file objects in that readline(-1) has no effect #7348Benjamin Peterson2009-12-131-0/+2
|
* convert usage of fail* to assert*Benjamin Peterson2009-06-301-1/+1
|
* Revert the fix for #1548891, it broke backwards compatibility with arbitrary ↵Georg Brandl2007-08-081-22/+0
| | | | | | read buffers. Fixes #1730114.
* Make cStringIO.truncate raise IOError for negativeMartin v. Löwis2006-11-191-0/+1
| | | | | arguments (even for -1). Fixes the last bit of #1359365.
* Bug #1548891: The cStringIO.StringIO() constructor now encodes unicodeGeorg Brandl2006-10-121-0/+22
| | | | | arguments with the system default encoding just like the write() method does, instead of converting it to a raw buffer.
* SF patch #1359365: cStringIO.StringIO.isatty() will raise a ValueErrorWalter Dörwald2006-03-151-0/+7
| | | | now if close() has been called before (like file and StringIO.StringIO do)
* SF patch #1359365: file and cStringIO raise a ValueError when next() is calledWalter Dörwald2006-03-151-0/+2
| | | | after calling close(). Change StringIO, so that it behaves the same way.
* Patches #1298449 and #1298499: Add some missing checks for errorMichael W. Hudson2005-09-221-0/+7
| | | | | | returns in cStringIO.c. Thanks to Andrew Bennetts. This must be a backport candidate.
* Add error checks for the bz2, cStringIO and operator modules.Walter Dörwald2004-11-011-0/+2
| | | | Add function names to various PyArg_ParseTuple calls in bz2module.c.
* Patch 1012740: cStringIO's truncate doesn'tTim Peters2004-08-211-1/+2
| | | | | | | | | | | | | 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.
* SF bug #770485: cStringIO does not set closed attrRaymond Hettinger2003-08-081-0/+10
|
* Combine the functionality of test_support.run_unittest()Walter Dörwald2003-05-011-4/+6
| | | | | | | | | | 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.
* SF patch 695710: fix bug 678519: cStringIO self iteratorRaymond Hettinger2003-04-241-3/+3
| | | | (requested by GvR. patch contributed by Michael Stone)
* Get rid of relative imports in all unittests. Now anything thatBarry Warsaw2002-07-231-1/+1
| | | | | | | | | | | 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. :)
* Make StringIO work in --disable-unicode builds...Michael W. Hudson2002-05-131-0/+2
|
* Whitespace normalization.Tim Peters2002-02-161-1/+1
|
* Restore Python 2.1 StringIO.py behaviour: support concatenatingMarc-André Lemburg2002-01-061-0/+15
| | | | | | Unicode string snippets to larger Unicode strings. This fix should also go into Python 2.2.1.
* A workaround for the missing buffer() builtin in jython.Finn Bock2001-12-091-0/+6
| | | | This closes patch "[ #490850 ] Jython and test_StringIO".
* test_iterator(): Don't do a type comparison to see if it's anBarry Warsaw2001-09-251-1/+4
| | | | | | iterator, just test to make sure it has the two required iterator protocol methods __iter__() and next() -- actually just test hasattr-ness.
* StringIO patch #462596: let's [c]StringIO accept read buffers onMarc-André Lemburg2001-09-241-8/+23
| | | | input to .write() too.
* Converted test_StringIO.py to use unittest, soBarry Warsaw2001-09-221-41/+71
| | | | | | | 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.
* In O_writelines: Replace use of string.joinfields with "".join.Jeremy Hylton2001-02-091-1/+7
|
* Added a test for the StringIO write() error I just fixed.Guido van Rossum2000-10-121-0/+7
|
* Jack Jansen reported that the regression test failed on the Mac whereGuido van Rossum2000-10-111-3/+1
| | | | | | | string.letters was much more than expected. Solution: explicit is better than implicit; don't rely on string.letters.
* Uncommented tests that failed for cStringIO,Jim Fulton2000-10-061-17/+11
| | | | Added missing clode to make the clode test test a close. ;)
* Added some tests for the truncate() method; one is commented out becauseFred Drake2000-09-281-0/+23
| | | | | | | | 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).
* New test cases for the StringIO moduleMartin v. Löwis2000-09-191-0/+15
generated by cgit v0.12 at 2024-11-24 08:56:13 (GMT)