Issue 1919: Backport of io.py (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/46214

classification

process

Created on 2008-01-24 11:41 by christian.heimes, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg61626 - (view)	Author: Christian Heimes (christian.heimes) *	Date: 2008-01-24 11:41
I've started on a back port of Python 3.0's io.py to Python 2.6. First results are promising. cd trunk svn cp ../py3k/Include/bytes_methods.h Include/ svn cp ../py3k/Objects/bytes_methods.c Objects/ svn cp ../py3k/Lib/io.py Lib/ svn cp ../py3k/Lib/test/test_io.py Lib/test/ svn cp ../py3k/Modules/_fileio.c Modules/ patch -p0 < trunk_io.patch I'm not sure how to proceed with the missing bytearray type: * backport bytearray and the new buffer interface from 3.0 * write a replacement for 2.6 * replace the bytearray code with new code
msg61630 - (view)	Author: Thomas Heller (theller) *	Date: 2008-01-24 13:33
> * backport bytearray and the new buffer interface from 3.0 backport of the new buffer interface is required for PEP 3118 which is marked accepted: " It is intended that this PEP will be back-ported to Python 2.6 by adding the C-API and the two functions to the existing buffer protocol. "
msg61646 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2008-01-24 18:11
Backporting bytearray should be relatively clean since it's a brand new type right?
msg64663 - (view)	Author: Georg Brandl (georg.brandl) *	Date: 2008-03-29 01:21
The bytearray branch has been merged.