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 vabr2
Recipients cjw296, gregory.p.smith, lisroach, mariocj89, michael.foord, rbcollins, rhettinger, terry.reedy, vabr2, veky, xtreak
Date 2020-12-10.09:45:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607593501.8.0.883608126177.issue41877@roundup.psfhosted.org>
In-reply-to
Content
https://github.com/python/cpython/pull/23729 is now a follow-up to improve docs and error message about the assert misspellings.

I'm now looking at the misspelled arguments: autospec and spec_set. These are accepted by patch, patch.object and patch.multiple, and spec_set is also accepted by create_autospec.

The three frequent misspellings I saw in our codebase are auto_spec, autospect and set_spec. I could add a check to look for them in kwargs, and also add an "unsafe" argument (default False), which, when True, disables the check. This would mimic what is already done for the misspelled asserts.
History
Date User Action Args
2020-12-10 09:45:01vabr2setrecipients: + vabr2, rhettinger, terry.reedy, gregory.p.smith, rbcollins, cjw296, michael.foord, veky, lisroach, mariocj89, xtreak
2020-12-10 09:45:01vabr2setmessageid: <1607593501.8.0.883608126177.issue41877@roundup.psfhosted.org>
2020-12-10 09:45:01vabr2linkissue41877 messages
2020-12-10 09:45:01vabr2create