18 Commits

Author	SHA1	Message	Date
Guido van Rossum	43713e5a28	Massive patch by Skip Montanaro to add ":name" to as many ... PyArg_ParseTuple() format string arguments as possible.	2000-02-29 13:59:29 +00:00
Guido van Rossum	17d53ecd8b	New version from Jim: don't call Py_FatalError() when initialization fails.	1999-06-15 14:35:48 +00:00
Guido van Rossum	68de0641ce	The writelines() function was never tested and contained numerous bugs ... (including a docstring saying "blah"). Fixed all this. (Please review for potential memory leaks!)	1999-02-08 17:03:27 +00:00
Guido van Rossum	476e49f055	Jim Fulton writes: ... This fixes a bug that can cause core dumps when doing seeks in input StringIO objects. This has a number of other clean-ups.	1998-12-15 21:43:15 +00:00
Guido van Rossum	3886bb6997	Add DL_EXPORT() to all modules that could possibly be used ... on BeOS or Windows.	1998-12-04 18:50:17 +00:00
Guido van Rossum	7d9b4133eb	New version from Jim Fulton: ... - New copyright. (Open source) - Fixed problem in seek method. The seek method should (and now does) fill with nulls when seeking past the end of the "file".	1998-11-25 16:17:32 +00:00
Guido van Rossum	2a502d8304	Use 'S' format character for the optional constructor argument, so we ... get a decent error message when it's not a string (instead of confusing errors when trying to use the thing).	1998-07-24 19:53:54 +00:00
Fred Drake	7589b71c4a	I_getattr(), ... O_getattr(): Added read-only access to the closed attribute, based on comment from Michael Scharf <Michael.Scharf@Rhein-Neckar.de>.	1998-07-17 14:30:58 +00:00
Fred Drake	10032ebb48	Module docstring indicated seek() isn't implemented, but it is.	1998-04-11 19:54:54 +00:00
Guido van Rossum	fdde96ce98	New versions of cPickle and cStringIO, from Jim Fulton's cPickle 1.0b1 ... distribution.	1997-12-04 01:13:01 +00:00
Guido van Rossum	9efe8ef7a1	#Plug small memory leaks in constructors.	1997-09-03 18:19:40 +00:00
Guido van Rossum	15a40394b0	Fix the bug Jeremy was experiencing: both the close() and the ... dealloc() functions contained code to free/DECREF the buffer (there were differences between I and O objects but the logic bug was the same). Fixed this be setting the buffer pointer to NULL and testing for that. (This also makes it safe to call close() more than once.) XXX Worry: what if you try to read() or write() once the thing is closed?	1997-09-03 00:09:26 +00:00
Guido van Rossum	142eeb8339	cPickle release 0.3 from Jim Fulton	1997-08-13 03:14:41 +00:00
Guido van Rossum	3dc35b0c66	My own patch: support writable 'softspace' attribute.	1997-04-11 19:56:06 +00:00
Guido van Rossum	154417e27b	Unknown changes by Jim Fulton.	1997-04-09 17:35:33 +00:00
Barry Warsaw	61a63e152d	Quieted gcc -Wall by removing unused local variables. ... Suppressing my urge to reformat according to Python coding standards! :-)	1997-01-14 17:38:28 +00:00
Guido van Rossum	55702f8d6a	Jim's latest version.	1997-01-06 22:57:52 +00:00
Guido van Rossum	049cd90b93	Jim F's brainchild	1996-12-05 23:30:48 +00:00