Guido van Rossum added the comment: Does anyone who was on this bug previously (e.g. the original author or the reviewers) know what was holding up the patch? Does it need more review? More tests? Is there any reason to reject fixing this at all? (I hope not.) As far as replacing the whole thing with a call into the other code goes, I'm hesitant if only because we don't have enough unit tests for the edge cases of the implementation that would be deleted, so if the wholesale replacement were to break user code we wouldn't find out until after it's been released. Fixing it seems less risky.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12411> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
