On 7/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I tried some tricks to get this working as I think it should to keep > backwards compatibility for those with special file naming > requirements. > > Please give some feedback and tell me if i'm way off course. :)
Hi Oyvind, Apologies for taking so long to get back to you on this issue. Regarding your suggestions for 'special file naming requirements': I agree that broad use case exists, but I can't say I particularly like any of the the implementations you propose. More design work is required here. On an organizational level, it would be better to open this as a new ticket, rather than piggyback it on #3297. #3297 is tracking a specific problem - the absence of FileFields in newforms. This problem needs to be fixed. Allowing 'special file naming requirements' is a feature addition that is separate to File Fields. While it is a nice feature, it is a separate feature, and no decision has been made on what this feature should look like - the plethora of options you provide shows that it is not a simple proposition. This feature will need to go through a separate design and review process. As such, it should be on a different ticket. This would also make following the patches much easier. It took me a while to work out exactly which parts of your latest patches were bugfixes to my FileField patch, and which were new and unrelated features. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
