Vaibhav Mallya <mally...@umich.edu> added the comment: Well, the reason I put in the inner row/col namedtuple initially was because the first mistake I made with the original module was mixing up the row/col indices for a particular case. It certainly caused all sorts of weird headaches. :o)
I mean, it seems like there's no real reason it "should" be (row,col) instead of (col,row) in the returned tuple; that is, it feels like the ordering is arbitrary in and of itself. I really feel that allowing for start.row and start.col would make the interface completely explicit and valid semantically. Agreed with the other two points, however. Also, I take it there's going to be a need for an addendum to the test suite, since the interface is being modified? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5857> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com