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 r.david.murray
Recipients Shay.Rojansky, barry, eric.smith, nafur, pierslauder, r.david.murray, terry.reedy
Date 2012-10-03.14:27:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349274429.09.0.95369959179.issue11245@psf.upfronthosting.co.za>
In-reply-to
Content
To fully answer the original question that opened this issue: contributions will be welcomed.  While I don't currently have time to work on imaplib myself, I have an interest and will review and if appropriate commit patches.

I like Shay's proposal, but absent a patch along those lines having blocking IMAP support will definitely be an improvement.  An application needing to monitor more than one imap connection could do its own threading.

Thanks for proposing the patch.  Could you please submit a contributor agreement?  I probably won't have time to fully consider the proposed patch for a bit, but I've put it on my todo list.  

test_imaplib does have a testing framework now, do you think you could write tests for the new feature?
History
Date User Action Args
2012-10-03 14:27:09r.david.murraysetrecipients: + r.david.murray, barry, terry.reedy, pierslauder, eric.smith, Shay.Rojansky, nafur
2012-10-03 14:27:09r.david.murraysetmessageid: <1349274429.09.0.95369959179.issue11245@psf.upfronthosting.co.za>
2012-10-03 14:27:09r.david.murraylinkissue11245 messages
2012-10-03 14:27:08r.david.murraycreate