I added that code to find and fix all instances of timezone warnings as it
turns the vague timezone warnings into full blown exceptions with stack
trace so that I could actually see the location in code where the warnings
occurred.  After fixing all warnings I left the code commented out as it is
no longer needed, but might be needed in the future. I will make sure to
explain this in the comments.



On Fri, Jul 12, 2013 at 10:28 AM, Piotr Mitros <notifications@github.com>wrote:

> In src/edinsights/settings.py:
>
> > @@ -192,3 +193,11 @@
> >          },
> >      }
> >  }
> > +
> > +##uncomment to provide full location of code that uses naive datetime
> > +#import warnings
> > +#warnings.filterwarnings(
> > +#        'error', r"DateTimeField received a naive datetime",
> > +#        RuntimeWarning, r'django\.db\.models\.fields')
> > +
>
> Instead of ignoring warnings, could we fix the issue? Or if not, can the
> comment explain why this is difficult to fix?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/insights/pull/7/files#r5165793>
> .
>