Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #105995
| From | Random832 <random832@fastmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: [stdlib-sig] Can imaplib be improved? |
| Date | 2016-03-29 13:22 -0400 |
| Message-ID | <mailman.163.1459272132.28225.python-list@python.org> (permalink) |
| References | <1458873222.2158998.559175002.3C7CEAF4@webmail.messagingengine.com> |
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. 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. Anyone have any thoughts?
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [stdlib-sig] Can imaplib be improved? Random832 <random832@fastmail.com> - 2016-03-29 13:22 -0400
Re: [stdlib-sig] Can imaplib be improved? Grant Edwards <invalid@invalid.invalid> - 2016-03-29 18:45 +0000
Re: [stdlib-sig] Can imaplib be improved? Random832 <random832@fastmail.com> - 2016-03-29 14:55 -0400
csiph-web