Andrey Golovizin wrote: > Jacob Kaplan-Moss wrote: > > "... with too many backwards-incompatible changes ..." -- as Hugo > > points out, this will break a lot of existing code. > Well, some day Django will have to switch to unicode anyway (even Python-3000 > is going to use unicode strings everywhere). Right now is a good time for it. > After 1.0 switching will be much more problematic.
and the first changes towards that will start appearing in python 2.5: http://www.python.org/dev/peps/pep-0332/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
