Tom, thank you for that very useful tip! My feeble python-fu has now been strengthened.
On Monday, December 17, 2012 8:27:28 AM UTC-6, Tom Evans wrote > > > Following the thread I see that you have figured out where and why > this is coming from. There is a simple tip you can use to speed this > up in future, simply run python with warnings set to error, and any > Warnings will be converted into RuntimeErrors - so you get a lovely > stack trace showing exactly how and when the warning was issued. > > You can configure python to stop only on certain Warnings, but the > simplest way is to turn all Warnings into Errors: > > python -W error manage.py .... > > Full details on what you can specify with -W here: > > http://docs.python.org/2/library/warnings.html#the-warnings-filter > > Cheers > > Tom > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/R9E0V7qFg5YJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
