On 28 Jun 2006, at 15:32, Adrian Holovaty wrote: > The only big problem I see is that it could confuse the (unfortunately > large) mass of programmers who don't understand Unicode yet. That is a > big potential pitfall.
That's very true. The documentation overhead will be considerable. It should be possible to get most things to Just Work, but the edge cases will be hard to explain. A classic example is working with a Python interactive prompt and trying to "print article.title" when title contains higher order unicode characters - this causes ascii decode errors in terminals that haven't been correctly configured. Having been bitten by unicode problems in the past while dealing with RSS feeds (from feedparser, which always returns unicode strings) I'd definitely love to see this feature in Django, and I'd be willing to help out with the effort. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
