happy-kitchen-89482
04/26/2025, 3:03 AMrun_rule_with_mocks
doesn’t work with call-by-name at the moment? At least that is what I’m seeing.happy-kitchen-89482
04/26/2025, 3:03 AMhappy-kitchen-89482
04/26/2025, 3:06 AMconcurrently()
awaiting multiple calls-by-namehappy-kitchen-89482
04/26/2025, 3:08 AMhappy-kitchen-89482
04/26/2025, 3:23 AMget()
helper on are the raw coroutines, not the Call
wrappers.happy-kitchen-89482
04/26/2025, 3:29 AMworried-painter-31382
04/26/2025, 10:02 AMrun_rule_with_mocks
has a place in call-by-nameworried-painter-31382
04/26/2025, 10:03 AMpytest-asyncio
works fineworried-painter-31382
04/26/2025, 10:05 AMconcurrently
complicates that option a little bit, but I think maybe deprecating run_rule_with_mocks
and providing a facility to mock concurrently
, possibly a patching context manager that just causes concurrently
to return the input arguments ~ as is would be much more intuitive in a unit test context.worried-painter-31382
04/26/2025, 10:07 AMMockGet
mirrors Get
, not call_by_name
.happy-kitchen-89482
04/26/2025, 11:42 AMhappy-kitchen-89482
04/26/2025, 4:51 PMCall
wrapper, not it’s underlying .rule.func
, and that thing is a field in a frozen dataclass so you can’t naively patch on that either…happy-kitchen-89482
04/26/2025, 4:51 PM