Carl Meyer added the comment: FWIW, my assumption was that the typical usage pattern would be `import mock` rather than separate imports of all the assertions, so I don't think there'd really be an increase in what users need to know about or import. (They already need to know about the methods on the mock object, knowing about functions in a module isn't practically any different.)
But the "breaking working code for insufficient benefit" argument is strong indeed, and personally I'm happy to defer to the module author on this one. Thanks for writing and maintaining mock! ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24651> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
