Nick Coghlan <ncogh...@gmail.com> added the comment: On a quick read through, the patch looks fine to me.
I actually agree it would be nice if we could keep the "quiet=True" default (since it is a better match for the feature set we want in our own tests), but I see the compatibility issue as a deal breaker for that idea. It's probably worth adding a comment to that effect at the top of the function implementation to help people coming along later and asking "why did they choose the 'wrong' default value?". ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8155> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
