On Tue, Nov 3, 2009 at 3: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. It may be interesting for others if you posted some examples of what you are used to doing in 2.x. Maybe somebody will suggest a better way of doing it in 3.x than you have thought of. :-) > I will convert to Py3, but not likely before summer. Besides 2to3, any > other tools/suggestions would be welcome. (Perhaps there is a Master switch > to disable Unicode? ;-) Yes, go back to 1.5.2. :-) -- --Guido van Rossum (python.org/~guido)
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