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
It appears r66103 introduced a regression - file objects are treated as
having an encoding, so non-ascii data fails. It was further complicated
by the fact that file objects in 2.6 have an 'encoding' attribute, but
by default it is None - so a 'hasattr' check for encoding doesn't work
the same.
The fix is quite trivial and I also added a new test to demonstrate the
error - but for the impatient, you can reproduce it via:
In all earlier versions of Python, the bytes as specified are written.
2.6 complains that 'None' is not a valid encoding and fails to write the
record.
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: