id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
31608	forms.DateTimeField parses ISO 8601 datetime with offset as aware when USE_TZ is False.	Carlton Gibson	Hasan Ramezani	"The following test fails on 3.1a1. 

> `USE_TZ`: If this is set to True, Django will use timezone-aware datetimes internally. Otherwise, Django will use naive datetimes in local time.

{{{
diff --git a/tests/forms_tests/field_tests/test_datetimefield.py b/tests/forms_tests/field_tests/test_datetimefield.py
index f0e6ada3c5..ed035497d8 100644
--- a/tests/forms_tests/field_tests/test_datetimefield.py
+++ b/tests/forms_tests/field_tests/test_datetimefield.py
@@ -2,8 +2,8 @@ from datetime import date, datetime
 
 from django.core.exceptions import ValidationError
 from django.forms import DateTimeField
-from django.test import SimpleTestCase
-from django.utils.timezone import get_fixed_timezone, utc
+from django.test import SimpleTestCase, override_settings
+from django.utils.timezone import get_fixed_timezone, is_naive, utc
 
 
 class DateTimeFieldTest(SimpleTestCase):
@@ -65,6 +65,12 @@ class DateTimeFieldTest(SimpleTestCase):
             with self.subTest(value=value):
                 self.assertEqual(f.clean(value), expected_datetime)
 
+    @override_settings(USE_TZ=False)
+    def test_use_tz_false(self):
+        f = DateTimeField()
+        value = '2014-09-23T22:34Z'
+        self.assertTrue(is_naive(f.clean(value)))
+
     def test_datetimefield_clean_invalid(self):
         f = DateTimeField()
         msg = ""'Enter a valid date/time.'""
}}}

Expected behaviour is to return a naive datetime. "	Bug	closed	Forms	3.1	Release blocker	fixed		Claude Paroz	Ready for checkin	1	0	0	0	0	0