Here's some usages of Cookie that show quite wide use still: http://www.google.com/codesearch?q=lang%3Apython+%22import+Cookie%22
>From the first few pages: mailman, zope, trac, roundup, cherrypy, chandler, turbogears, myghty, paste, moin, mod_python etc. Not that that's the only reason why you wouldn't remove it... just backing up Ians assertion that Lots of web frameworks use it. cu. On Feb 4, 2008 10:41 AM, Ian Bicking <[EMAIL PROTECTED]> wrote: > Brett Cannon wrote: > > As part of the standard library cleanup for Python 3.0, it has been > > suggested to me that the Cookie module be removed. The rationale for > > this is that most of the module is already deprecated and cookielib > > does a better job for cookie support anyway. > > > > I just wanted to see if anyone here had strong objections (along with > > reasons) as to why the module should be kept around in some form or > > another. > > I think most frameworks still use the Cookie module. The cookielib > module is more oriented to the client side. It doesn't seem to have the > same parsing functions that you'd use on the server side (though maybe > they are there and just not documented because they also exist in the > Cookie module). > > Ian > > _______________________________________________ > Web-SIG mailing list > Web-SIG@python.org > Web SIG: http://www.python.org/sigs/web-sig > Unsubscribe: http://mail.python.org/mailman/options/web-sig/renesd%40gmail.com > _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
