Path: csiph.com!weretis.net!feeder6.news.weretis.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: [stdlib-sig] Can imaplib be improved? Date: Tue, 29 Mar 2016 18:45:42 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 38 Message-ID: References: <1458873222.2158998.559175002.3C7CEAF4@webmail.messagingengine.com> NNTP-Posting-Host: 67-130-15-94.dia.static.qwest.net X-Trace: reader1.panix.com 1459277142 10117 67.130.15.94 (29 Mar 2016 18:45:42 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 29 Mar 2016 18:45:42 +0000 (UTC) User-Agent: slrn/1.0.2 (Linux) Xref: csiph.com comp.lang.python:105996 On 2016-03-29, Random832 wrote: > I'd posted this to stdlib-sig@python.org without realizing that that > list is mostly dead. > > On Thu, Mar 24, 2016, at 22:33, Random832 wrote: >> I assume that everyone who has ever used imaplib is familiar with how >> painful its output format is to deal with. Yes. Been there, done that, still have bald patches where I tore my hair out. >> I am wondering if anyone else has any ideas on ways it can be >> extended in a backward-compatible way to provide options for better >> parsing, handling unilateral data from the server, processing data >> as it comes in, etc. I think giving up on backwards compatiblity and starting from scratch is the best idea. I like imaplib2 https://pypi.python.org/pypi/imaplib2 https://github.com/bcoe/imaplib2 https://sourceforge.net/projects/imaplib2/ imapclient is pretty nice to work with: https://pypi.python.org/pypi/IMAPClient https://bitbucket.org/mjs0/imapclient http://freshfoo.com/presentations/imapclient-intro/#/ Perhaps it (or something like it) could be added to the std library alongside the current imaplib. -- Grant Edwards grant.b.edwards Yow! I'm reporting for duty at as a modern person. I want gmail.com to do the Latin Hustle now!