Bug #2114
should use unicode throughout the code instead of str
| Status: | New | Start date: | 10/17/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.3 | |||
| Component: |
Description
Since email addresses can be UTF-8, KeySync should be able to handle that. Right now, the internal format is str, it should use unicode. Perhaps the easiest way to achieve this would be to switch to Python 3, which I think is natively unicode.
History
#1 Updated by abeluck over 4 years ago
Python 3 support for modules is still not totally there. For example, PIL doesn't support python 3 and probably won't ever, since PIL is essentially dead. Pillow (the PIL fork) aims to support python3, but they aren't there yet. That's just PIL. I'm sure we have other modules that don't support python 3 either.
We should employ the decode early, unicode everywhere, encode late, strategy for this super presentation about unicode in python < 3.