Nothing definitive, but from checking the location of the code that is raising the warning, I suspect one of the following:
1. USE_TZ is not set in your production code, but _is_ set in your settings file for your tests. Of course, your code should work either way for the most flexibility. 2. The test database you are using (ie, from fixtures or otherwise) has non-timezone dates and times, and USE_TZ is set in your testing settings files. In these cases your test data and the USE_TZ setting should be matching. On Friday, December 14, 2012 11:43:09 AM UTC-8, bobhaugen wrote: > > Thanks for the reply. > > On Friday, December 14, 2012 1:27:03 PM UTC-6, Chris Cogdon wrote: >> >> Would be nice to know what function's raising that error, and where the >> value came from. Requesting traceback, database type (tried it with more >> than one database type), and other information. >> >> It's in a test. No real traceback, just a bunch of the same error > messages: > > ./manage.py test valueaccounting > Creating test database for alias 'default'... > /home/bob/.virtualenvs/vn2/lib/python2.6/site-packages/django/db/models/fields/__init__.py:808: > > RuntimeWarning: DateTimeField received a naive datetime (2012-12-14 > 19:41:27.469600) while time zone support is active. > RuntimeWarning) > /home/bob/.virtualenvs/vn2/lib/python2.6/site-packages/django/db/models/fields/__init__.py:808: > > RuntimeWarning: DateTimeField received a naive datetime (2012-12-14 > 19:41:27.507916) while time zone support is active. > RuntimeWarning) > > Database is sqlite. > -- 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/-/S59utK7wxy4J. 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.
