On 1 mars 2012, at 18:12, Aymeric Augustin wrote:
> Sure, I'll take care of this.
See https://docs.djangoproject.com/en/dev/topics/i18n/timezones/#fixtures
Feel free to comment on #17738 or open a new ticket if you have more questions.
Best regards,
--
Aymeric.
--
You received this message b
2012/3/1 Jacob Kaplan-Moss
> Aymeric Augustin wrote:
> > Indeed, a fixture that was generated with USE_TZ = False (or before time
> > zone support existed) will raise warnings when it's loaded with USE_TZ =
> > True.
>
> Ahha - I've been seeing that warning and haven't been able to interpret
> it
Aymeric Augustin wrote:
> Indeed, a fixture that was generated with USE_TZ = False (or before time
> zone support existed) will raise warnings when it's loaded with USE_TZ =
> True.
Ahha - I've been seeing that warning and haven't been able to interpret
it yet.
Can we possible change the warning
2012/3/1 Yo-Yo Ma
> django/db/models/fields/__init__.py:808: RuntimeWarning: DateTimeField
> received a naive datetime (2012-01-01 00:00:00) while time zone support is
> active.
>
> The above warning is caused by a JSON fixture having "2012-01-01 00:00:00"
> for a DateTimeField timestamp.
>
Inde
django/db/models/fields/__init__.py:808: RuntimeWarning: DateTimeField
received a naive datetime (2012-01-01 00:00:00) while time zone support is
active.
The above warning is caused by a JSON fixture having "2012-01-01 00:00:00"
for a DateTimeField timestamp.
Does this mean that fixture loadin
