Message374362
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. |
|
Date |
User |
Action |
Args |
2020-07-27 06:40:04 | cjw296 | set | recipients:
+ cjw296, michael.foord, mariocj89, xtreak, webisteme |
2020-07-27 06:40:04 | cjw296 | set | messageid: <1595832004.49.0.0771950070513.issue41403@roundup.psfhosted.org> |
2020-07-27 06:40:04 | cjw296 | link | issue41403 messages |
2020-07-27 06:40:03 | cjw296 | create | |
|