From ddff6522fa72aacc7475ba5cd4bf8683ff12b8c7 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Sun, 13 Oct 2013 11:54:11 +0200 Subject: [1.6.x] Fixed #19560 -- Identified field in warning for naive datetime. Thanks gcc for the report and vajrasky for the patch. Backport of 570d9c2678d6cc564f9c70138554af8f7ce9ec49 from master. --- docs/topics/i18n/timezones.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt index 5ed60d0a94..4652e7e9c1 100644 --- a/docs/topics/i18n/timezones.txt +++ b/docs/topics/i18n/timezones.txt @@ -431,14 +431,15 @@ code: :func:`~django.utils.timezone.now`, Finally, in order to help you locate code that needs upgrading, Django raises a warning when you attempt to save a naive datetime to the database:: - RuntimeWarning: DateTimeField received a naive datetime (2012-01-01 00:00:00) while time zone support is active. + RuntimeWarning: DateTimeField ModelName.field_name received a naive + datetime (2012-01-01 00:00:00) while time zone support is active. During development, you can turn such warnings into exceptions and get a traceback by adding the following to your settings file:: import warnings warnings.filterwarnings( - 'error', r"DateTimeField received a naive datetime", + 'error', r"DateTimeField .* received a naive datetime", RuntimeWarning, r'django\.db\.models\.fields') Fixtures -- cgit v1.3