On Mon, Jul 1, 2013 at 6:18 PM, Russell Keith-Magee <russ...@keith-magee.com > wrote:
> >> Agreed. >> >> Also, just to clarify, I think we should stick with Django's policy of >> only supporting naive time objects, for the reasons you cited earlier in >> this thread. >> >> So, any timezone support we would add to the time filter should only >> support aware datetime objects, not aware time objects. >> >> Correct? >> > > Yes - that sounds like the right approach to me. > > Done. https://code.djangoproject.com/ticket/20693 is ready for somebody to review it. It would be great if this could get into 1.6. -- Warren Smith -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
