On 2/15/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > I tried to show that it leaves out only two things: > > - if DEFAULT_CHARSET is different than DB charset it won't work (but > it's a weird situation, most legacy systems have one legacy encoding for > both) > > - it doesn't help if unicode is actually put into models or in raw SQL > manually but this bug was never about it anyway and won't break anything > since it fixes newforms, not backends
Hi Ivan, Could you explain again why you think newforms should output clean_data as bytestrings rather than Unicode strings? If I understand your argument correctly, you're saying newforms should be rolled back to bytestrings because the rest of the framework isn't Unicode-aware yet. Are you suggesting that we would convert newforms clean_data *back* to being Unicode *after* we convert the rest of the framework to be Unicode-aware? I apologize in advance if you've already brought this up and explained it. Just trying to understand your thinking here. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
