@6730d36f @f29919fc @c5389096 Too much magic at a distance. Practically, magic parameter name matching as a modularity mechanism will never not be extremely jarring to me. Aesthetically, byte-code rewriting to change the semantics of a little-used piece of dedicated syntax seems bananas. It’s been a problem exactly twice in my entire career so it’s not like I am tripping over bytecode modification bugs all the time but it seems like a wildly unnecessary risk even if it’s vanishingly small. 

 @0a734d30 I can completely understand your position. I’m currently trying to demystify some of the magic in a project I inherited 

 @6730d36f I used to really advocate against it, but at this point I am resigned to just being a weirdo on this point. It’s fine, the abstractions work okay once you’ve gotten used to them, but I will probably not choose it voluntarily unless I specifically know that colleagues in this context specifically want to use it 

 @0a734d30 @6730d36f I’m a weirdo with you @0a734d30. I 110% agree about the magic action at a distance and the name matching. But what alternative do you use? 

 @4c2fcda1 @6730d36f Usually, Twisted's `trial` test runner, but this advice may not generalize :)

(Seriously though come maintain trial with me we could make it so much better)