Paul Hummer <p...@eventuallyanyway.com> added the comment: I've been doing a review of this patch for the last few hours. There are a few issues that need to be taken care of in order for it to move forward, and I'm currently working on them, in this order:
1. Update the patch to the most recent svn. The most current patch is almost 5 years old. I've ported it forward. 2. Fix the unittests. The patch is failing its unittests currently, and so I'm fixing the unittests, and will be adding tests where there may not be any coverage. 3. Implement the suggestions made by alberanid and kbk, adding tests where necessary. I've been chatting with jafo, and am willing to commit to maintaining this code for the next few years, and am willing to sign the contributor agreement in order to do so. I don't particularly want to step on anyone's toes, so if someone else is also working on this, I'm happy to hand off what I've already been working on. ---------- nosy: +rockstar _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1054967> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
