Yes, I discovered the problem was my TIME_ZONE setting did not match
the system time zone,
and I'm on Windows.
I think the comment about offset-naive only applies to cases where you
supply
an optional comparison date, but it doesn't say so.
On May 9, 1:38 pm, George Song wrote:
> On 5/9/2009 11
On 5/9/2009 11:28 AM, adrian wrote:
>
> This filter is returning an empty string for a valid date (or datetime
> with 0,0,0 added) in
> Django 1.0.2.
>
> The documentation for this says:
>
>> Comparing offset-naive and offset-aware datetimes will return an empty
>> string.
>
> but it doesn't
This filter is returning an empty string for a valid date (or datetime
with 0,0,0 added) in
Django 1.0.2.
The documentation for this says:
> Comparing offset-naive and offset-aware datetimes will return an empty string.
but it doesn't say which type it uses.
Shouldn't this say something like:
3 matches
Mail list logo
