On Fri, May 15, 2009 at 8:28 AM, Lior Gradstein <lior.gradst...@gmail.com>wrote:
> > I find it really disturbing for someone that comes for the first time > and *thinks* that's it's possible (especially when it was possible in > 1.0, and you'll get a lot of references on the web on 'tips' and > similar usage) to access the filenames in a pre_save signal. > > The problem is that *if* you don't know that it's impossible now, > you'll try to access instance.myattribute.path (which contained the > correct path to the file in Django 1.0) and get a result, but a wrong > one! Isn't it possible to prevent access to the attribute or at least > set it to something that will not be interpreted as "strange"? > > I too am concerned that we've done something that quietly breaks existing working code. I'm OK with the new behavior -- file name is not known until after model is saved -- but what about alerting users whose code relies on the old behavior? I assume we will have something in the release notes, but I fear some people will miss it, or not recall they coded something this way. Can we make attempted access to the path attribute fail loudly if it's done before the file is actually saved to disk? Karen --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
