Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upGet mock coverage back to 100% #18228
Conversation
…to ever be exectuted.
This comment has been minimized.
This comment has been minimized.
Now that https://bugs.python.org/issue39485 is resolved, this PR is the last blocker for the 4.0 release of the backport. Since there have been no complaints, I'm going to go ahead and merge it. |
This comment has been minimized.
This comment has been minimized.
bedevere-bot
commented
Jan 29, 2020
|
This comment has been minimized.
This comment has been minimized.
It's not clear to me what's actually failed in the buildbot above? Anyone able to enlighten me? |
cjw296 commentedJan 28, 2020
I wish there was a way to enforce coverage on mock in cpython, it's so easy to slip and always introduces dead code, at best, and bugs at worst.
I'm neutral on whether or not this should be backported to 3.8 or 3.7, however I would like to land this soon as possible so we can get mock 4.0 out and get a lot more feedback on all the AsyncMock stuff :-)