This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients Julian, Mariatta, brett.cannon, chris.jerdonek, daniel.urban, eric.araujo, ezio.melotti, martin.panter, michael.foord, pablomouzo, parkouss, pitrou, r.david.murray, rbcollins, rhettinger, ta1hia, xtreak
Date 2019-09-11.08:12:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I concur with Raymond here. Since mock is also part of stdlib and this issue predates mock being merged to stdlib. I think adding it to unittest sort of expands the unittest API being just an alias to mock.patch. mock.patch is used in lot of places and has a good adoption as plain function, decorator and context manager. This would also mean explaining people why there is mock.patch and TestCase.patch in docs too.
Date User Action Args
2019-09-11 08:12:03xtreaksetrecipients: + xtreak, brett.cannon, rhettinger, pitrou, rbcollins, ezio.melotti, eric.araujo, r.david.murray, michael.foord, pablomouzo, daniel.urban, chris.jerdonek, Julian, martin.panter, parkouss, Mariatta, ta1hia
2019-09-11 08:12:03xtreaksetmessageid: <>
2019-09-11 08:12:03xtreaklinkissue11664 messages
2019-09-11 08:12:02xtreakcreate