Skip Montanaro wrote: > Neil> Shouldn't we be heading to a world where __str__ always returns > Neil> unicode objects? > > Which reminds me... Didn't someone (MAL?) add an experimental configure > flag or something similar to allow building Python with PyString* == > PyUnicode* (or something like that)? I think the idea was to see what needs > to be fixed before Python can become 100% Unicode. Last I recall it was > lots. The option is -U, and it causes string literals to be treated as Unicode objects. Currently, it gets so far as to start the interactive interpreter. Regards, Martin
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