On Tue, Nov 3, 2009 at 6:27 PM, Larry Bugbee <bugbee at seanet.com> wrote: > This is my problem to solve... I work with a lot of [non-production] crypto > where byte strings are a normal way of manipulating and storing keys and > other artifacts. Under Python2 I have few/no Unicode issues. With > Python3's default string type being Unicode, there are a lot of subtle ways > where my codes go south. Like I say, it is my problem. > Interesting- I've been doing crypto in python 3 for quite some time and haven't had any issues except with getting things to play nicely with C. Any specific examples? Geremy Condra
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4