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 cjw296
Recipients cjw296, mariocj89, michael.foord, webisteme, xtreak
Date 2020-07-27.06:40:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595832004.49.0.0771950070513.issue41403@roundup.psfhosted.org>
In-reply-to
Content
Given that `mock.patch` is being used incorrectly here, the error message seems clear enough: It's saying there's a `Foo` object in place, and `rsplit` gives a strong indication that a string was expected.

Would adding type hints in mock.py be a resolution for this?

I'd be fine to see this bug closed with "wontfix", but will leave it open for now in case others feel strongly differently.
History
Date User Action Args
2020-07-27 06:40:04cjw296setrecipients: + cjw296, michael.foord, mariocj89, xtreak, webisteme
2020-07-27 06:40:04cjw296setmessageid: <1595832004.49.0.0771950070513.issue41403@roundup.psfhosted.org>
2020-07-27 06:40:04cjw296linkissue41403 messages
2020-07-27 06:40:03cjw296create