I have just finished merging the Unicode branch into trunk (in r5609). This should be backwards-compatible for all practical purposes (providing you only use ASCII data). The only real difference you will notice in that case is that model fields are Unicode strings instead of bytestrings in type, but since they are ASCII data anyway, that shouldn't make any real difference.
For people wanting to take advantage of non-ASCII data now, there are some quick porting steps at http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist . There is more extensive documentation in the files docs/unicode.txt in the source or online at http://www.djangoproject.com/documentation/unicode/ . Anybody who was previously using the Unicode branch to develop against, should "svn switch" back to trunk, as no further updates will be going into that branch. Thankyou to this group of early adopters for your early testing feedback. Regards, Malcolm -- Two wrongs are only the beginning. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
