You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2005-10-03.01:19:09.000>created_at=<Date2004-02-25.19:30:42.000>labels= ['invalid', 'expert-unicode']
title='File read of Chinese utf-16-le treats upper byte 1A as EOF'updated_at=<Date2005-10-03.01:19:09.000>user='https://bugs.python.org/rrother'
I believe there is a misconception here: the open(..., "r")
will cause the file to be opened in C lib's text mode. Since
UTF-16 is binary data, this will lead to problems with line
breaking
and file handling in general.
MAL, this seems to come up from time to time. Perhaps we
should update the doc for open()? If it's already
documented, could we make it clearer? Then we should be
able to close this bug. I think I saw another bug recently
that was similar to this one.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: