This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients docs@python, eli.bendersky, eric.araujo, terry.reedy
Date 2011-07-12.04:55:14
SpamBayes Score 4.5196347e-11
Marked as misclassified No
Message-id <1310446515.57.0.426026056.issue12434@psf.upfronthosting.co.za>
In-reply-to
Content
In my opinion, it's the error messages and docstrings that should be changed, not the documentation. This module was introduced in 2.6 and moves on to 2.7, and there's no reason to have it throw confusing errors for the sake of easier back-patching from 3.x

However, when I run this example on 2.6, I get:

   TypeError: can't write str to text stream

Which (arguably) makes sense, since the docs explicitly say that "Text I/O classes work with unicode data."
History
Date User Action Args
2011-07-12 04:55:15eli.benderskysetrecipients: + eli.bendersky, terry.reedy, eric.araujo, docs@python
2011-07-12 04:55:15eli.benderskysetmessageid: <1310446515.57.0.426026056.issue12434@psf.upfronthosting.co.za>
2011-07-12 04:55:15eli.benderskylinkissue12434 messages
2011-07-12 04:55:14eli.benderskycreate