Great! Thank you Tom and Russ for the heads up.
Cheers, AT On 7/20/11, Tom Evans <[email protected]> wrote: > On Wed, Jul 20, 2011 at 3:24 AM, Russell Keith-Magee > <[email protected]> wrote: >> The problem here actually lies with Python. >> >> For some reason, Python 2.7 changed the reporting behavior of Warnings >> so that DeprecationWarning is ignored by default [1]. So, because >> you're developing in Python 2.7, you don't see the warnings by >> default; in production, where you're using Python 2.5, you do. >> >> [1] http://docs.python.org/library/warnings.html#warning-categories >> >> Yours, >> Russ Magee %-) > > Thanks Russ, that explains it perfectly. For the archives, you can > override this on the command line, eg: > > python -W once manage.py etc > > Which gives me a lot of lovely warnings to work through :) > > Cheers > > Tom > > -- > You received this message because you are subscribed to the Google Groups > "Django users" 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-users?hl=en. > > -- Sent from my mobile device -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
