Christian Mancini

I should not use `@override` annotation since is not supported before Python 3.12 and also use mypy locally first.

> * Don't do the friends things if it only hides the actual usage of the mocks in the tests. Okay, I'edit the set up to use a function that...

Added a testing library to express better assertions with containers...I'm working in the various steps @kaste Isn't sufficient to use ```bash rye add --dev assertpy ```

> 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....

@kaste Hello, what do you think? I still need to implement the context manager and the unstub. Do you think that we should support a workflow like this?: ```python a...

> The old InOrder supported only one mock, and your implementation supports proper cross-mock interactions? My implementation supports cross-mock interaction like ```python in_order.verify(cat).meow() in_order.verify(dof).bark() ``` but doesn't yet supports an...

@kaste I' happy with the implementation and tests. Let me know if you need any changes or some documentation to put in the docs with examples (and how you wanted)....

> * Also if `verify(cat).say(...)` catches all invocations. What is the purpose of operator `...`?

Things I can't do - Make the sign of `inorder verify` the same as `verify` because i delegate to the original with fixed arguments so changing arguments will lead to...

> `in_order.verify(first_mock.a_method())` calls `rv = first.method()` and then calls `in_order.verify(rv)`. I made a mistake, the call is the same as the actual `verify` ```python in_order.verify(first_mock).a_method() ``` I have extended the...