On 10/16/07, Doug Van Horn <[EMAIL PROTECTED]> wrote: > > On Oct 16, 7:06 am, "Fco. Javier Nievas" <[EMAIL PROTECTED]> wrote: > > Could you give a link to that patch? > > > > Thanks > > One last note, there's a link at the bottom of my post to Marty's > patch. Here it is if you'd rather just head there: > > http://code.djangoproject.com/ticket/5361
Whoops! I thought for sure I had included a link. Thanks for that, Doug. Your approach at solving this problem is quite interesting, actually. You seem to have actually managed to find a reason to keep _save_FIELD_file() around. Unfortunately, that's not a very compelling reason for the long term, since it especially has problems when dealing with a model with multiple FileFields (the same _save_FIELD_file() will be used for both fields). In #5361, we'll be moving that processing away from _save_FIELD_file() and into a custom file object, which you've probably already discovered by looking at the patch. Your patch would still continue for a while, since _save_FIELD_file() isn't going away yet, but it may well disappear at some point, so it's better to have a proper solution in place. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
