A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112260.html below:

[Python-Dev] Draft PEP: Deprecate codecs.StreamReader and codecs.StreamWriter

[Python-Dev] Draft PEP: Deprecate codecs.StreamReader and codecs.StreamWriter [Python-Dev] Draft PEP: Deprecate codecs.StreamReader and codecs.StreamWriterVinay Sajip vinay_sajip at yahoo.co.uk
Thu Jul 7 10:49:22 CEST 2011
Nick Coghlan <ncoghlan <at> gmail.com> writes:

> Unless somebody steps forward to fix them, the Stream* classes have to
> go (albeit with a suitable period of deprecation). They're *actively
> harmful* in their current state, so retaining the status quo is not a
> viable option in this case.

I can understand that there might be specific issues with them, but isn't
"actively harmful" a little strong? I don't see who is being actively harmed by
them, nor how.

Regards,

Vinay Sajip



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4