Comment 2 for bug 1122897

So I went ahead and merged this to trunk, and then switched back to standard Base32 encoding using the new compatibility functions in dbase32.rfc3548.

That way we can move forward with dropping Python 3.2 support and being as ready as possible to switch to D-Base32, even thought we're not quite ready to make the switch.