Hi all, I've been looking at #5553 [1] tonight; it looks to be a good patch to fix some Datetime serialization issues that have arisen recently.
[1] http://code.djangoproject.com/ticket/5553 It's a fairly small change, but I'm still coming to terms with the finer points of the unicode changes, so I wanted to get a sanity check that I wasn't going to do something with unexpected consequences. force_unicode() provides the strings_only option, which allows you to convert an object to a unicode string, leaving 'non-strings' unmodified. In this context 'non-strings' are specifically defined as NoneType, int and long. The proposed patch modifies this list of non-strings, adding DateTime, Time and floats. Is there any particular reason that smart_unicode checks explicitly for int, long and None? Would there be any side effects to adding DateTime, Time and float to the list of 'non strings'? Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
