Opened 5 years ago

Last modified 4 years ago

#2638 new enhancement

Encodings for all Change Sources

Reported by: dustin Owned by:
Priority: patches-accepted Milestone: 0.9.+
Version: Keywords: simple, encoding
Cc:

Description

All change sources take data from somewhere else, and in many cases that data arrives in the form of bytestrings. By the time that data makes it to the data API's addChange method, it needs to be unicode. Some change sources already handle this, using an 'encoding' parameter to indicate the encoding expected for any bytestrings. However, other change sources - notably, those in mail.py, don't. Those change sources should be tested, then fixed to handle bytestrings correctly.

Change History (1)

comment:1 Changed 4 years ago by dustin

  • Milestone changed from 0.9.0 to 0.9.+
  • Priority changed from major to patches-accepted
  • Summary changed from [nine] Encodings for all Change Sources to Encodings for all Change Sources
Note: See TracTickets for help on using tickets.