[Python-Dev] Status of the PEP 400? (deprecate codecs.StreamReader/StreamWriter) (original) (raw)
Guido van Rossum guido at python.org
Thu Jul 28 01:38:26 CEST 2011
- Previous message: [Python-Dev] Status of the PEP 400? (deprecate codecs.StreamReader/StreamWriter)
- Next message: [Python-Dev] Status of the PEP 400? (deprecate codecs.StreamReader/StreamWriter)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Jul 27, 2011 at 4:11 PM, Victor Stinner <victor.stinner at haypocalc.com> wrote:
Le 28/07/2011 00:36, Guido van Rossum a écrit :
Sorry Victor, I somehow didn't see that message even though I received it (I probably thought it was a continuation of the python-dev thread which I've been ignoring). No problem. no, there's no particular hurry That's why it's a deprecation process and the removal is schedule for later: "3.4 (or maybe later)". I added "or maybe later" before reopening a new thread on this list.
That still sounds fairly aggressive.
no, I don't think you should change codecs.open() to call io.open() The PEP is useless without this change. If we don't deprecate any class and don't change codecs.open(), it's better to just reject the PEP.
Why? (Not that I am against rejecting the PEP. I feel weakly opinioned in this case, about -0.)
start deprecating them formally once we feel that most users have switched Users of codecs.open() or users of codecs.Stream* classes?
I would think both. Is there any reason to continue using codecs.open()?
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] Status of the PEP 400? (deprecate codecs.StreamReader/StreamWriter)
- Next message: [Python-Dev] Status of the PEP 400? (deprecate codecs.StreamReader/StreamWriter)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]