07/02/11 Yasushi Masuda<[EMAIL PROTECTED]> wrote: > Instead, I'd like to propose making get_valid_filename() as default > behaviour of ``filename_normalization``, and adding a > ``filename_nomalizer`` parameter in FileField's constructor, like this::
I completely agree with Yasushi. The point is to avoid patching django's core model code every time. Proposal of Yasushi is the most realistic, I think. It's not breaking backward compatibility and it's loose coupling from base models. And it doesn't need to discuss which encoding is the best for that purpose;-) I drop my proposal and patch. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
