summaryrefslogtreecommitdiffstats
path: root/Modules/_fileio.c
Commit message (Collapse)AuthorAgeFilesLines
* Merged revisions 67052 via svnmerge fromChristian Heimes2008-10-301-2/+4
| | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/trunk ........ r67052 | christian.heimes | 2008-10-30 22:26:15 +0100 (Thu, 30 Oct 2008) | 1 line Issue #4237: io.FileIO() was raising invalid warnings caused by insufficient initialization of PyFileIOObject struct members. ........
* Issue #3945: Fixed compile error on cygwin. (initializer element is not ↵Hirokazu Yamamoto2008-09-231-1/+1
| | | | | | constant) Reviewed by Amaury Forgeot d'Arc.
* #3703 unhelpful _fileio.FileIO error message when trying to open a directoryBenjamin Peterson2008-09-011-1/+3
| | | | Reviewer: Gregory P. Smith
* #3662: Fix segfault introduced when fixing memory leaks.Neal Norwitz2008-08-241-1/+1
| | | | | TESTED=./python -E -tt ./Lib/test/regrtest.py test_fileio R (approach from bug)=Amaury and Benjamin
* Fix:Neal Norwitz2008-08-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | * crashes on memory allocation failure found with failmalloc * memory leaks found with valgrind * compiler warnings in opt mode which would lead to invalid memory reads * problem using wrong name in decimal module reported by pychecker Update the valgrind suppressions file with new leaks that are small/one-time leaks we don't care about (ie, they are too hard to fix). TBR=barry TESTED=./python -E -tt ./Lib/test/regrtest.py -uall (both debug and opt modes) in opt mode: valgrind -q --leak-check=yes --suppressions=Misc/valgrind-python.supp \ ./python -E -tt ./Lib/test/regrtest.py -uall,-bsddb,-compiler \ -x test_logging test_ssl test_multiprocessing valgrind -q --leak-check=yes --suppressions=Misc/valgrind-python.supp \ ./python -E -tt ./Lib/test/regrtest.py test_multiprocessing for i in `seq 1 4000` ; do LD_PRELOAD=~/local/lib/libfailmalloc.so FAILMALLOC_INTERVAL=$i \ ./python -c pass done At least some of these fixes should probably be backported to 2.5.
* Issue #3139: Make buffer-interface thread-safe wrt. PyArg_ParseTuple,Martin v. Löwis2008-08-121-6/+9
| | | | | | | by denying s# to parse objects that have a releasebuffer procedure, and introducing s*. More module might need to get converted to use s*.
* fix issue3304 - remove an incorrect PyMem_Free in fileio_initGregory P. Smith2008-07-061-1/+0
|
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-12/+12
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-12/+12
|
* Backport fast alternate io.BytesIO implementation.Alexandre Vassalotti2008-05-091-48/+16
| | | | | Merged r62778, r62779, r62802, r62806, r62807, r62808, r62809, r62844, r62846, r62952, r62956.
* Remove all traces of HAVE_STRERROR.Brett Cannon2008-03-181-8/+0
| | | | | The removal of strerror.c led to the function check being removed from configure.in.
* Backport of several functions from Python 3.0 to 2.6 including ↵Christian Heimes2008-01-251-0/+927
PyUnicode_FromString, PyUnicode_Format and PyLong_From/AsSsize_t. The functions are partly required for the backport of the bytearray type and _fileio module. They should also make it easier to port C to 3.0. First chapter of the Python 3.0 io framework back port: _fileio The next step depends on a working bytearray type which itself depends on a backport of the nwe buffer API.
generated by cgit v0.12 at 2024-11-22 13:24:43 (GMT)