[issue22128] patch: steer people away from codecs.open

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22128] patch: steer people away from codecs.open

Irit Katriel added the comment: Since Martin corrected the docs in issue 19548 for python 3, and python 2 is no longer relevant, I believe this can be closed. -- nosy: +iritkatriel resolution: -> duplicate status: open -> pending superseder: -> 'codecs' module docs improvements

[issue22128] patch: steer people away from codecs.open

Martin Panter added the comment: Just pointing out there is a patch for Issue 19548 for Python 3 which also adds a pointer to the builtin open() function and updates the codecs.open() caveats. That issue doesn’t touch Python 2 though. -- nosy: +vadmium

[issue22128] patch: steer people away from codecs.open

Changes by Frank van Dijk fwvd...@gmail.com: Added file: http://bugs.python.org/file36273/codecsopen2a.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22128 ___

[issue22128] patch: steer people away from codecs.open

Changes by Frank van Dijk fwvd...@gmail.com: Added file: http://bugs.python.org/file36274/codecsopen3a.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22128 ___

[issue22128] patch: steer people away from codecs.open

Antoine Pitrou added the comment: I don't think it's useful to tell people: * use codecs.open() on Python 2.4, 2.5, 2.6 * use io.open() on Python 2.7 (io is too slow on 2.6 to be a real alternative to codecs.open()) * use open() on Python 3.4+ Instead we can tell them to use io.open() on

[issue22128] patch: steer people away from codecs.open

Frank van Dijk added the comment: Marc-Andre Lemburg added the comment: Pointing people to io.open() as alternative to codecs.open() is a good idea, but that doesn't make codecs.open() less useful. The reason why codecs.open() uses binary mode is to avoid issues with automatic newline

[issue22128] patch: steer people away from codecs.open

New submission from Frank van Dijk: stackoverflow.com has a zillion answers recommending the use of codecs.open() as a unicode capable drop in replacement for open(). This probably means that there is still a lot of code being written that uses codecs.open(). That's bad thing because of

[issue22128] patch: steer people away from codecs.open

Changes by Frank van Dijk fwvd...@gmail.com: Added file: http://bugs.python.org/file36235/codecsopen3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22128 ___

[issue22128] patch: steer people away from codecs.open

Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +doerwalter, haypo, lemburg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22128 ___ ___

[issue22128] patch: steer people away from codecs.open

STINNER Victor added the comment: See also my PEP 400: http://legacy.python.org/dev/peps/pep-0400/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22128 ___

[issue22128] patch: steer people away from codecs.open

Marc-Andre Lemburg added the comment: Pointing people to io.open() as alternative to codecs.open() is a good idea, but that doesn't make codecs.open() less useful. The reason why codecs.open() uses binary mode is to avoid issues with automatic newline conversion getting in the way of the