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 pitrou
Recipients benjamin.peterson, edreamleo, pitrou
Date 2008-08-18.16:00:56
SpamBayes Score 1.1354528e-05
Marked as misclassified No
Message-id <1219075257.86.0.56360168489.issue3590@psf.upfronthosting.co.za>
In-reply-to
Content
> Just to be clear, I am at present totally confused about io streams :-)

Python 3.0 distincts more clearly between unicode strings (called "str"
in 3.0) and bytes strings (called "bytes" in 3.0). The most important
point being that there is no more any implicit conversion between the
two: you must explicitly use .encode() or .decode().

Files opened in binary ("rb") mode returns byte strings, but files
opened in text ("r") mode return unicode strings, which means you can't
give a text file to 3.0 library expecting a binary file, or vice-versa.

What is more worrying is that XML, until decoded, should be considered a
byte stream, so sax.parser should accept binary files rather than text
files. I took a look at test_sax and indeed it considers XML as text
rather than bytes :-(

Bumping this as critical because it needs a decision very soon (ideally
before beta3).
History
Date User Action Args
2008-08-18 16:00:57pitrousetrecipients: + pitrou, benjamin.peterson, edreamleo
2008-08-18 16:00:57pitrousetmessageid: <1219075257.86.0.56360168489.issue3590@psf.upfronthosting.co.za>
2008-08-18 16:00:57pitroulinkissue3590 messages
2008-08-18 16:00:56pitroucreate