Author vstinner
Recipients ezio.melotti, lemburg, serhiy.storchaka, vstinner
Date 2017-03-10.15:46:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYQK-Pu3YU-2q13Wh30=QL489nioqpp5FuKynNpqAy+2Q@mail.gmail.com>
In-reply-to <1489158705.54.0.207796689698.issue29783@psf.upfronthosting.co.za>
Content
Serhiy Storchaka added the comment:
> I agree that it is better to use directly the module implementing the codecs. But old third-party code still can use non-text codecs.
>
> There should be good reasons for breaking backward compatibility. Wouldn't be better to deprecate codecs.open()?

I'm not sure that I understood. Do you consider that using
codecs.open() with a non-text codecs is a "legit" use case or not?

I understood that you suggest a smoother transition using a
deprecation to give more time to developers to update their code.

But what do you want to deprecate? The whole codecs.open() function?
Or using non-text codecs with codecs.open()? Or using text codecs with
codecs.open()?
History
Date User Action Args
2017-03-10 15:46:26vstinnersetrecipients: + vstinner, lemburg, ezio.melotti, serhiy.storchaka
2017-03-10 15:46:26vstinnerlinkissue29783 messages
2017-03-10 15:46:26vstinnercreate