Nick Coghlan added the comment: Perfect is the enemy of good. I vote for just committing it, then Chris can propose additional fixes/changes in a subsequent patch. On 26 Feb 2013 09:52, "Chris Jerdonek" <rep...@bugs.python.org> wrote:
> > Chris Jerdonek added the comment: > > > I still fail to understand what are you trying to achieve. > > My goal is to reach consensus on changes and have them committed. In its > current form, I don't agree with the patch. The length of the comment > thread and the length of the patch has discouraged me from raising most of > my comments, because I'm fairly certain my comments will lead to > back-and-forth discussion which will make the thread even longer. That's > why I want to break things up. > > I want to be clear that I'm not against the goals of the patch, so I'm not > trying to "block" or stalemate anything. I just have concerns I would > like to discuss which is what the review process is supposed to allow. > Needless to say, I know what it feels like to have a patch reviewed in > detail (which I'm not necessarily planning to do). On the plus side, it's > much better than comments being against the patch outright in any form. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue14468> > _______________________________________ > ---------- _______________________________________ 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
