Wonderful, thanks a lot for the answer :) cheers, Thomas On Thu, Jan 20, 2011 at 12:07 AM, Gabriel Hurley <[email protected]> wrote: > If you try this in any of the more recent versions (sorry I don't know > exactly when this was changed) you'll get a ViewDoesNotExist exception > telling you which view in which module it couldn't find. If you have DEBUG = > True you'll get a nice Django 500 error debug page giving you everything you > need to diagnose the problem. If you have DEBUG = False you'll get an > exception in your error log that you can use to debug. This will happen > regardless of whether or not the invalid function is actually called or > referenced by your templates or other code. > And for the record, there's absolutely nothing wrong with using strings > instead of actual functions in your URLConf. In fact, I would go so far to > say that it is the *preferred* method, and that's why it's in the tutorial. > The tutorial (to the best of our abilities) does not contain anything that > the core team and/or the community considers "bad practice". > > Try it out with a current version of Django. If you think there's something > more that should be added, feel free to write back. > All the best, > - Gabriel > > -- > 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. >
-- 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.
