It seems to me a setting is not the way to go, but a custom storage would be better. I've made a custom storage the computes the md5 of the content and uses that as the directory of the file, though that generate a whole lot of directories. In a lot of ways, I think it would be great if django could try to check to see if the duplicate files also have the same content and re-use the first file if so. Otherwise I'm still in the mindset that filename_1, filename_2 is an improvement over filename_, filename__, filename___. :).
It would be nice if upload_to functions had access to the file content. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/79f70121-9449-4b72-b89b-f3842950b399%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
