Eric Smith <e...@trueblade.com> added the comment: This would be easier to review if the patch were generated with 'svn diff'.
That said, it looks okay in concept to me, although I couldn't apply it and test without manually mucking with the patch. 2.6 is in bugfix mode, so it can't be changed there. I added 3.2, since it should probably agree with 2.7. What I can't answer is if this should actually be done. I don't know if anyone's relying on the current behavior. I do agree that unified diffs are more desirable. ---------- nosy: +eric.smith priority: -> low stage: -> patch review type: -> behavior versions: +Python 3.2 -Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8355> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
