Olli Paakkunainen

@adarshk7, I think it's hard to make the language always to flow naturally when the methods are chained. For example, `expect_call('function').with_args('a', 2)` make sense but `expect_call('function').and_return(3)` doesn't sound so natural...

`expectation.and_return(re='r+')` would not work if there are multiple return values. Also, it would be good to be consistent with `with_args` and in there we need to use the parameters from...

How about this: `"/stu.*/"` == `re.compile("stu.*")` `"//stu.*//"` == `"/stu.*/"` Then if someone needs to use double forward slash in the beginning and end of a pattern, they can just use...

Hi! I usually do this when I have to check for some specific arg: ```python flexmock.should_receive("method").with_args(str, str, "some_arg", int).once() ``` This will allow to ignore other args if the types...

@wojtha, thank you for your suggestions. I added a warning to the documentation in PR #127. I think before we raise a warning when `new_instances` method is called, we should...

Hi! Right now MethodSignatureErrors are raised instantly when the method is called with a wrong signature. I think it would make more sense to raise the errors in during flexmock...

> @ollipa I think this PR can be closed, the code has changed so much, and the original issue is probably not valid anymore ? I re-enabled some globally disabled...

I tried the examples in those issues but none of them use the the `yield self` functionality. The line is here: https://github.com/flexmock/flexmock/blob/3edc739258652d876a9f7d01775f658b9e6fbc03/src/flexmock/api.py#L92 Maybe that fix affected just Python2?

Sure add me to the assignees :ok_hand:

Thank you for the detailed bug report! I will take a look at this when I have time.