A little more research shows that I could also accomplish what I'm looking for by tying into the pre_init or post_init signal, but then I'd need a customized function for each field that needs processing, on each model. This could be done, of course, and it would certainly keep this coercion out of the core, but I can't imagine it would be considered elegant (or even preferable) in any way. Someone prove me wrong.
I guess I'll sum up my thoughts on this another way. I don't see to_python as explicitly converting strings to other data types, but rather as converting a storage data type to a usable data type. Of course, that's not the way it is, but rather the way I think it should be. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
