On 16 Jul 2008, at 01:14, Jeremy Dunck wrote:

>
> On Tue, Jul 15, 2008 at 6:56 PM, Malcolm Tredinnick
> <[EMAIL PROTECTED]> wrote:
>>
>>
>> On Tue, 2008-07-15 at 18:49 -0500, Jeremy Dunck wrote:
>>> I was using HttpResponse.set_cookie for the first time and annoyed
>>> that expires has to be a properly-formatted string.
>>>
>>> Why not take a datetime and do the formatting in the function?
>>>
>>> Obviously this is a breaking change, unless we have an isinstance  
>>> for
>>> backwards incompatibility.
>>
>> Yeah, we should do something sensible if passed a datetime. Can you  
>> open
>> a ticket?
>
> http://code.djangoproject.com/ticket/7770
>

It would be nice if there were global cookie domain/path/secure/age  
settings that could be applied. Somehow SESSION_COOKIE_DOMAIN doesn't  
seem suitable, what with sessions being an optional component.

Ben

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to