Chris Jerdonek added the comment: > But, surely at this point, it would be easier to get meaningful additional > review after the current set of changes are committed rather than continually > redoing a large set of patches.
This was my reason for asking early on that the changes be proposed and committed individually, so that the whole set of patches doesn't have to be redone after each round of comments: http://bugs.python.org/issue14468#msg179849 But the bulk of the discussion wound up being about this request rather than on the content of the patches themselves. I've never had a problem breaking up my own issues/patches when asked. For various reasons, there is a phenomenon that the larger the patch, the less relative scrutiny it tends to undergo (with the exception of PEP's where the process is different), which is the opposite of what it should be. I'd like for us to try to avoid that. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14468> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
