Sean Reifschneider added the comment: Patch looks good to me. Fred?
Comments on "should I do more fixes": Just straight documentation changes are, in my experience, fairly likely to be processed quickly. Changes to the code may take quite a lot more discussion. Smaller, individual patches are likely to be taken much more than large mega patches that change many things. So, my recommendation would be to do individual efforts: Fix the current documentation, fix "XXX fix me" parts, do enhancements. I understand where you're coming from, I spent a full day implementing string.rsplit() including documentation, only to have it languish for around a year before other people re-opening the rejected submission finally got it accepted. However, python definitely benefits from the attention. Sometimes things do get dropped, because of other commitments from the maintainers. Assign your issue that has been ignored to me and I'll take a look at it. ---------- assignee: -> fdrake keywords: +patch nosy: +fdrake, jafo priority: -> normal versions: +Python 2.6 __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1172> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com