You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking about the idea of moving imaplib2 to the Python 3 standard libs. That idea was done by Maxim Khitrov here [1] but had some problems here [2]. I would like to propose it again.
I all of us agree it, we can start to update the impalib2 code to make the imaplib and imaplib2 interface compatible (for backward compatibility). We need check the imaplib patches that can apply in imaplib2,.... Perhaps we can send some patches to the imaplib standard lib.
That is new for me. We should think about this if we decide migrate. Also, we should check how many applications are using the stdlib-imaplib, piers-imaplib2 and mxk-imaplib2 [1]
Ideally, we should implement a new "imaplib2 interface" layer, which lets us use all 3 IMAP4 libraries! User can select his preferred library! Default would be piers-imaplib2! But at the higher level, they should all ultimately accomplish the same tasks and achieve the exact same result, on the 1IMAP41 server! Which would be verified by means of tests which run in Travis-CI against the top 10 most popular IMAP4 servers!
Hi,
I was thinking about the idea of moving imaplib2 to the Python 3 standard libs. That idea was done by Maxim Khitrov here [1] but had some problems here [2]. I would like to propose it again.
I all of us agree it, we can start to update the impalib2 code to make the imaplib and imaplib2 interface compatible (for backward compatibility). We need check the imaplib patches that can apply in imaplib2,.... Perhaps we can send some patches to the imaplib standard lib.
What do you think?
Happy new year!
Best regards,
kix
[1] https://python-ideas.python.narkive.com/dgZhBV1Y/new-imaplib-implementation-for-python-3-2-standard-library
[2] https://python-ideas.python.narkive.com/dgZhBV1Y/new-imaplib-implementation-for-python-3-2-standard-library#post18
The text was updated successfully, but these errors were encountered: