Optionally support leaving UTF8 strings as UTF8 encoded str objects rather than converting to UCS16/32 unicode objects

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I think this will improve performance and without sacrificing safety since a lot of code, file formats, and protocols are designed to deal with utf8 strs. Also, if your app's native output is utf8 you currently have to convert both to and from unicode objects.

            Assignee:
            Unassigned
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: