I'm having to add calls that look like this to my code so that stuff doesn't blow up when passing model strings to other libraries:
oldsteadylib.func( smart_str(str) ) # forcing unicode back to bytestring Ouch. Ugly. Reminds me of the bad old days of working with strings in C++. >From what I read, in Python 3, the default character encoding will be UTF-8 and this should obviate the need for writing conversions and using other ugly syntax to differentiate between string encodings. In the meantime, is there a configuration setting that I can use to disable unicode for django until I want to deal with special unicode syntax, if ever? I've also read that you can change your system wide encoding from ASCII to UTF-8 by changing the setencoding() in /usr/lib/python2.5/site.py. Would anyone recommend this approach? Again, my goal is to keep the strings in my code clean from special conversions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
