<br><br><div class="gmail_quote">On Wed, Jul 27, 2011 at 04:48, Maxim Khitrov <span dir="ltr"><<a href="mailto:max@mxcrypt.com">max@mxcrypt.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Tue, Jul 26, 2011 at 10:09 PM, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>
><br>
><br>
> On Sun, Jul 24, 2011 at 18:06, Maxim Khitrov <<a href="mailto:max@mxcrypt.com">max@mxcrypt.com</a>> wrote:<br>
>><br>
>> Hello python-ideas,<br>
>><br>
>> My most recent project lead me down a path that eventually ended up at<br>
>> a new implementation of imaplib based on [RFC-3501]. Although I<br>
>> started the project by gradually adding functionality to the existing<br>
>> IMAP4 library, some of the features that I required simply could not<br>
>> be merged in (without breaking everything). As a result, I wrote my<br>
>> own version of the library, which incorporates all existing<br>
>> functionality of imaplib and includes many of my own improvements.<br>
>><br>
>> I wrote a PEP-style readme file that describes all the details of why<br>
>> the library was written and how it works, which is available from my<br>
>> mercurial repository:<br>
>><br>
>> <a href="http://hg.mxcrypt.com/python/imaplib2/raw-file/tip/README" target="_blank">http://hg.mxcrypt.com/python/imaplib2/raw-file/tip/README</a><br>
>><br>
>> The same repository also contains the library code and an example<br>
>> script that you can run if you have access to an IMAP4 server:<br>
>><br>
>> <a href="http://hg.mxcrypt.com/python/imaplib2/" target="_blank">http://hg.mxcrypt.com/python/imaplib2/</a><br>
>><br>
>> Is there any interest in adding my code to a future version of Python<br>
>> 3.x standard library?<br>
><br>
> Since no one has pointed you to it, there is a doc explaining what it takes<br>
> to get a new module added to the stdlib:<br>
> <a href="http://docs.python.org/devguide/stdlibchanges.html#adding-a-new-module" target="_blank">http://docs.python.org/devguide/stdlibchanges.html#adding-a-new-module</a> .<br>
<br>
</div></div>Thanks, I actually found and read that page before making my initial<br>
announcement. For now, I'm making the module available under the<br>
simplified BSD license to anyone who wishes to use it. If it has<br>
gained some traction over the next year, I'll be happy to submit it to<br>
PSF under Apache License 2.0. Is there anything else I should do in<br>
the mean time? How do I go about moving the development into the<br>
Python's infrastructure, or does that happen later?<br></blockquote><div><br>Later; the module has to first get traction enough for python-dev to even consider adding it. Basically the community needs to have decided as a whole that your module is the best solution for the job and that its API is stable and done evolving.<br>
<br>Hope this doesn't sound too negative, but we just have to be very cautious about what goes into Python's stdlib.<br><br>-Brett<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Over the next week or so, I'll finish writing the higher-level<br>
interface, which actually did end up inheriting from Mailbox, but with<br>
some limitations that I'll explain later. After that, I'll put<br>
together a test suite and update the documentation. The last remaining<br>
bit will be to implement some additional extensions and authentication<br>
methods. Don't have anything else planned beyond that.<br>
<br>
- Max<br>
</blockquote></div><br>