Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | This reverts r63675 based on the discussion in this thread: | Gregory P. Smith | 2008-06-09 | 1 | -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 PyBytes | Christian Heimes | 2008-05-26 | 1 | -12/+12 |
| | |||||
* | Backport fast alternate io.BytesIO implementation. | Alexandre Vassalotti | 2008-05-09 | 1 | -48/+16 |
| | | | | | Merged r62778, r62779, r62802, r62806, r62807, r62808, r62809, r62844, r62846, r62952, r62956. | ||||
* | Remove all traces of HAVE_STRERROR. | Brett Cannon | 2008-03-18 | 1 | -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 Heimes | 2008-01-25 | 1 | -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. |