summaryrefslogtreecommitdiffstats
path: root/Modules/_io
Commit message (Collapse)AuthorAgeFilesLines
* Buffered I/O: optimize lock taking in the common non-contended case.Antoine Pitrou2009-11-011-3/+5
|
* Roll back ill-considered attempts to fix printf specifier mismatch for off_t.Mark Dickinson2009-10-292-26/+9
| | | | | The sensible solution seems to be to implement %lld for PyString_FromFormat(V) and PyErr_Format. See issue #7228.
* Fix format specifier for MSVCMark Dickinson2009-10-281-1/+1
|
* Replace long long with PY_LONG_LONGMark Dickinson2009-10-281-2/+2
|
* Silence gcc warnings when trying to print an off_t using "lld", on platformsMark Dickinson2009-10-272-3/+14
| | | | where off_t has type long (e.g., 64-bit Linux).
* Use correct conversion specifier and length modifier when printing anMark Dickinson2009-10-262-8/+14
| | | | integer of type off_t. Also, don't assume that long long is available.
* Fix compilation error in debug mode.Antoine Pitrou2009-10-241-3/+0
|
* Manual py3k backport: [svn r74316] Issue #5449: Fix io.BytesIO to not accept ↵Antoine Pitrou2009-10-241-1/+3
| | | | arbitrary keywords
* Manual py3k backport: [svn r74158] Issue #6218: Make io.BytesIO and ↵Antoine Pitrou2009-10-242-9/+260
| | | | io.StringIO picklable.
* Manual py3k backport: [svn r74155] Issue #6242: Fix deallocator of ↵Antoine Pitrou2009-10-242-6/+10
| | | | io.StringIO and io.BytesIO
* Fix compilation warning on Windows, where size_t is 32bit but file offsets ↵Amaury Forgeot d'Arc2009-10-051-6/+7
| | | | are 64bit.
* Issue #6236, #6348: Fix various failures in the io module under AIXAntoine Pitrou2009-09-212-7/+7
| | | | | | | and other platforms, when using a non-gcc compiler. Patch by egreen. In addition, I made explicit the signedness of all bitfields in the IO library.
* #6750: TextIOWrapped could duplicate output when several threads write to it.Amaury Forgeot d'Arc2009-08-291-4/+9
| | | | this affect text files opened with io.open(), and the print() function of py3k
* Issue #6629: Fix a data corruption issue in the new `io` package, which couldAntoine Pitrou2009-08-061-0/+13
| | | | | | | | occur when writing to a BufferedRandom object (e.g. a file opened in "rb+" or "wb+" mode) after having buffered a certain amount of data for reading. This bug was not present in the pure Python implementation. Yes, this is a serious issue.
* Issue #4856: Remove checks for win NT.Hirokazu Yamamoto2009-06-281-5/+2
|
* backport r73430Benjamin Peterson2009-06-141-9/+0
|
* Issue #6215: backport the 3.1 io libAntoine Pitrou2009-06-128-0/+9244