Hey all, I recently came across the issue described in #5903 [1] earlier. There are two distinct patches that fix the problem, but at different levels. My inclination is to fix this issue at the model field level and properly override get_default. My feeling is that allowing Decimal objects to pass through force_unicode (when strings_only=True) might cause ill-effects in other parts of Django, but I am not entirely sure (running the test suite with the fix in force_unicode didn't cause any failed test, but that doesn't make it right to me :). I don't see much reason to do so. Perhaps someone can shed some light on this?
[1]: http://code.djangoproject.com/ticket/5903 -- Brian Rosner http://oebfare.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 -~----------~----~----~----~------~----~------~--~---
