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.

Title: Imaplib
Type: enhancement Stage: resolved
Components: Library (Lib) Versions: Python 3.10
Status: closed Resolution: postponed
Dependencies: Superseder:
Assigned To: Nosy List: rodolfogarciap, steven.daprano
Priority: normal Keywords:

Created on 2020-12-26 20:56 by rodolfogarciap, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (2)
msg383828 - (view) Author: Rodolfo García Peñas (rodolfogarciap) Date: 2020-12-26 20:56

Is it possible to move the imaplib2 implementation ( as imaplib stdlib?

What steps should I do?

msg383833 - (view) Author: Steven D'Aprano (steven.daprano) * (Python committer) Date: 2020-12-27 01:31
Are you the owner of imaplib2?

If so, you need to ensure that there are no licencing or copyright issues preventing imaplib2 being transferred into the stdlib. That may (or may not) require you to get agreement from any contributors to the library. That will depend on the licencing agreement your contributors have with you.

If you are not the owner, then you need to get the owner's agreement first, before you do anything else. We're not going to just *take* the library, or fork it.

That means that the imaplib2 library will have to adhere to Python's release schedule, our code of conduct, our policies on backwards compatibility, etc.

If the owner(s) agree that they are interested, then you can propose the idea on the Python-Ideas mailing list for discussion:

If there is interest in your proposal, then you can ask for a core developer to sponsor a PEP. Once you have a sponsor, you can write a PEP, and the steering council will rule whether or not to accept it.
Date User Action Args
2022-04-11 14:59:39adminsetgithub: 86917
2020-12-27 01:31:06steven.dapranosetstatus: open -> closed

nosy: + steven.daprano
messages: + msg383833

resolution: postponed
stage: resolved
2020-12-26 20:56:28rodolfogarciapcreate