Jacob Kaplan-Moss wrote: > * Forms: the newforms library is coming along nicely. There's some work that > remains, the bulk of which lies in converting the admin to use newforms > instead of manipulators. At that point, the transition can really be called > complete.
it seems that noone mentioned unicode in this discussion yet... does this mean, that the plan is to have django-1.0 still use bytestrings? because if yes, then i would recommend to "downgrade" newforms to bytestrings too. the reason is consistency... if i'm not mistaken, newforms works internally in unicode, and also outputs unicode... which is quite nice, but the problem is, the rest of django is in bytestrings... so, at the end, in a django-view: - GET/POST is in bytestrings - newforms outputs unicode - the templates output bytestrings - the db-api outputs bytestrings it is true, that with various hacks the newforms can be used from the bytestring-based templates, and also they can save models to the bytestring-based db-api. but it is not nice. the other way is to switch django to unicode completely. from the past discussion it seems, that many people wanted to work on it , patches were created, so i think the unicode-conversion could happen in a reasonable time. gabor --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
