Handle unicode (2.x) and bytes (3.x)

Issue #18 new
Nick Coghlan
repo owner created an issue

_str_base is defined, but not actually used. This means the API only accepts "str", even though it should also accept "bytes" in 3.x and "unicode" in 2.x

For the actual library, this should just require using _str_base correctly (the os module will take care of any necessary conversions), but the test suite updates are a little more involved.

Comments (0)

  1. Log in to comment