Context Navigation

Changes between Initial Version and Version 1 of Ticket #34699, comment 17

-              initial
+              v1
 Without a proper notion of typing / distinct types for Django naive vs aware datetime fields it is quite hard to make the experience better here. The way things are currently designed `DateTimeField` is expected to be naive if `USE_TZ = False` and aware otherwise, there's no way to represent naive `DateTimeField` at the ORM level when `USE_TZ = True`.
+Even on Postgres which has distinct types for naive and aware timestamps (`timestamp` and `timestamptz`) there's no warning emitted when mixing both; [https://dbfiddle.uk/xyLSKpNO it simply defaults to the globally configured timezone].
+Even on Postgres which has distinct types for naive and aware timestamps (`timestamp` and `timestamptz`) there's no warning emitted when mixing both; [https://dbfiddle.uk/xyLSKpNO it simply defaults to the globally configured timezone] like it's the case on Python
+{{{#!python
+>>> timezone.now() > datetime.datetime.now()
+TypeError: can't compare offset-naive and offset-aware datetimes
+}}}
 > Personally I feel the code should behave differently, but I don't see clearly how such fix would look or we would handle the potential deprecation/behavior change.