Eyal Posener added the comment: Thanks for the review, Michael.
About the use case: I use it for a process with loads code and inspect it's classes and methods. When I run this process, not always I have all the dependencies of the inspected code, so I found myself mocking all those packages before running the inspection code. This was very inconvenience, and broke any time someone added a new dependency to the code which is not in the standard library. About the name: I agree. About the keyword for the mock constructor: no problems. Should I fix the code and submit an updated patch? Do you think this function has a place in the standard mock module? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27376> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
