Changes by Petri Lehtinen pe...@digip.org:
--
nosy: +petri.lehtinen
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8796
___
___
Python-bugs-list
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
title: Deprecate codecs.open() - Deprecate codecs.open(), codecs.StreamReader
and codecs.StreamWriter
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8796
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
status: - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8796
___
___
Marc-Andre Lemburg m...@egenix.com added the comment:
Closing the ticket again.
We still need codecs.open() to support applications that target Python 2.x and
3.x.
You can reopen it after Python 2.x has been end-of-life'd.
--
resolution: - postponed
status: open - closed
STINNER Victor victor.stin...@haypocalc.com added the comment:
Le lundi 23 mai 2011 à 16:11 +, Marc-Andre Lemburg a écrit :
We still need codecs.open() to support applications that target Python 2.x
and 3.x.
io.TextIOWrapper exists in Python 2.6 and 2.7, and 2to3 can simply
replace
Marc-Andre Lemburg m...@egenix.com added the comment:
Correcting the title: this ticket is about codecs.open(), not StreamRead and
StreamWriter, both of which are essential parts of the Python codec machinery
and are needed to be able to implement per-codec implementations of codecs
which
Antoine Pitrou pit...@free.fr added the comment:
TextIOWrapper() is conceptually something completely different. It's
more something like StreamReaderWriter().
That's a rather strange assertion. Can you expand?
TextIOWrapper supports read-only, write-only, read-write, unseekable and
seekable
Marc-Andre Lemburg m...@egenix.com added the comment:
Antoine Pitrou wrote:
Antoine Pitrou pit...@free.fr added the comment:
TextIOWrapper() is conceptually something completely different. It's
more something like StreamReaderWriter().
That's a rather strange assertion. Can you expand?
