Bjørn Stabell wrote: > What if the patch required everything to be Unicode, meaning: > > * all programmers would have to become aware of Unicode to some extent > * all code would suffer the (minior) performance penalty of encoding > and decoding all text
The second point is arguable. Currently there are many cases where conversion is done twice. For example to check the length of any string field in validator it should be decoded to unicode, counted and then encoded back to bytes because it's what users expect in views. Same with string processing filters in templates. By converting internals to unicode we are requiring conversion everywhere between outside and inside but removing these double conversions at the same time. So this may be a performance gain as much as a loss. But anyway this seems to me absolutely negligible in practice. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
