Chris Withers <ch...@withers.org> added the comment:
Gregory, I find your response a little troubling. Myself and Karthikeyan both do a lot of work on Mock, some might even say we're the maintainers of Mock in both cpython's core repo and the backport. We both feel this belongs standalone on pypi, and would prefer not to see this merged. "We've been using these internally at Google for years" is not a compelling argument and suggests you already have a viable solution which doesn't involve merging these into the core repo. Your phrasing could be interpreted as somewhat bullying - "it's right for Google, so I'm going to do it for all of Python in spite of comments from other core contributors, and I don't want to discuss this on a mailing list because that will take too long". Please consider re-closing this issue and respecting the decisions of those of us who maintain mock long-term. If not, please suggest a way forward to mediate this disagreement, but please do not unilaterally merge anything without sorting this out first. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40133> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
