herr kaste

(I usually do the tests first. E.g what behavior do I even expect for all the cases. Do they all make sense in concerto.)

``` a) probably valid and we have two separate "lines" of recorded executions with InOrder(cat) as a, InOrder(dog) as b: b) a = InOrder(cat) b = InOrder(cat) # raises? already...

``` cat = mock() dog = mock() with InOrder(cat) as in_order: dog.bark() cat.meow() in_order.verify(dog).bar() # raises ```

> a = InOrder(cat) b = InOrder(cat) # raises? already registered Yeah, that should probably *not* raise. Nesting should ideally work, we need to ensure instead that nesting works.

Generally, this project predates any of the modern tools, like rye, uv etc. Don't do these distracting things here. They don't help you implement the actual thing. For this new...

Isn't that the meat of the re-implementation of InOrder? ``` cat = mock() dog = mock() when InOrder(cat, dog) as in_order: cat.meow() dog.bark() cat.meow() in_order.verify(cat).meow() in_order.verify(dof).bark() in_order.verify(cat).meow() ``` The old...

I pushed master to update to modern tooling (`uv`) and generally towards v2. Please try a rebase. E.g. `RememberedInvocation | RememberedProxyInvocation` is now `invocation.RealInvocation`.

* What does it take to support the full signature of the original `verify` function? * `...` means: any arguments * What "things" did you not understand?

Difficult to think this through... The standard verify should be supported at least.

`in_order.verify(first_mock.a_method())` calls `rv = first.method()` and then calls `in_order.verify(rv)`. How do you want to implement that?