This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author B. Kyven
Recipients B. Kyven, demian.brecht, maxy@debian.org
Date 2013-03-07.17:00:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362675623.45.0.542618536987.issue17251@psf.upfronthosting.co.za>
In-reply-to
Content
I now realized LWPCookieJar is a subclass of CookieJar but it behaves differently. I believe there are other quirks I haven't discovered, like expire=None which cause exception in LWPCookieJar, but works fine for CookieJar. Sadly the doc didn't mention them.

The official python document introduced 2 file cookiejar, one is Mozilla's FileCookieJar, which is explicitly advised as depricated.
LWPCookieJar which is human-readable seems the only advisable chooice to me. But it turns out not that simple.
My guess is that not many people use this module, or the expire=None problem and this dot question should be quite easy to spot on google. 

So forks, could your suggest how does other python user deal with cookie storage. Do they just pickle the cookie objects and save to file?
Or any via 3rd party cookie batteries? What's their pro/cons ? 

LWPCookie's usage is strage to me and ,I believe, many average users, I guess many people like me will be willing to know alternatives.
History
Date User Action Args
2013-03-07 17:00:23B. Kyvensetrecipients: + B. Kyven, maxy@debian.org, demian.brecht
2013-03-07 17:00:23B. Kyvensetmessageid: <1362675623.45.0.542618536987.issue17251@psf.upfronthosting.co.za>
2013-03-07 17:00:23B. Kyvenlinkissue17251 messages
2013-03-07 17:00:23B. Kyvencreate