Key was never an keyword argument. It was the cookies name, that variable got 
renamed to name in the cleanup.

1.5:

    def set_cookie(self, name, value='', max_age=None,
                   path='/', domain=None, secure=False, httponly=False,
                   comment=None, expires=None, overwrite=False)

1.4:

    def set_cookie(self, key, value='', max_age=None,
                   path='/', domain=None, secure=False, httponly=False,
                   comment=None, expires=None, overwrite=False)


> On Jul 26, 2015, at 15:11 , Iain Duncan <[email protected]> wrote:
> 
> Hi Bert, I don't know if it should be this way, but I got a hard error (not 
> just a warning) from webob.response.set_cookie that "key" is not a valid 
> keyword argument. This broke a pyramid app, but maybe I'm using a deprecated 
> api there? 
> 
> I was doing
> 
> response = Response()
> response.set_cookie(
>   key="my cookie",
>   ....
> )
> 
> thanks
> Iain
> 
> 
> 
> On Sat, Jul 25, 2015 at 6:29 PM, Bert JW Regeer <[email protected]> wrote:
> Hey everyone,
> 
> I have just released a brand new alpha of WebOb 1.5.0, it contains a lot of 
> exciting new changes that may impact your web application, please do thorough 
> testing and file bug reports if anything goes awry. I’ll be doing a longer 
> soak test with alpha’s and beta’s for this release cycle than previous cycles.
> 
> The biggest change is that cookie handling now follows RFC6265, for now it 
> will warn if you have warnings turned on, eventually those warnings will be 
> turned into errors, this will eventually break backwards compatibility for 
> those people relying on being able to create UTF-8 cookies for example 
> without first serializing to base64.
> 
> Further changes and bug fixes can be found here: 
> http://webob.readthedocs.org/en/latest/news.html#a0-2015-07-25
> 
> Enjoy, and please report any issues you find to the issue tracker at 
> https://github.com/Pylons/webob/issues
> 
> Thanks,
> Bert JW Regeer
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/pylons-discuss.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/pylons-discuss.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to