Pekka Klärck

Could you clarify why that would be beneficial compared to what's already possible by using keyword teardown?

I prefer test setup/teardown being executed once per test. Even if you were able to convince me that they should be run for each templated iteration, changing the behavior would...

This sounds more like a browser feature for me, and personally I'm fine pressing Ctrl-R, but if it would be opt-in I don't see problems adding such functionality. Do you...

Could you clarify the use case for this issue? I think we actually did support returning from user keywords with custom exceptions but removed that support because it was strange...

Do I get it right that your real use case is executing things on Python so that you get keywords visible in log? That at least seems to be the...

The example above has these two lines that I don't understand: ```python rf.eq(1, 2) # in the robot log will fail 'inner kw', 'outer kw' and 'some kw' but will...

Like with #3706, my current thinking is that adding the functionality requested in this issue isn't a good idea. That said, an API that allows Python based keywords to created...

Sounds good to me but need to decide where to add this API. This isn't trivial so I put this into RF 5.0 scope and will look at this when...

RF 5.0 release is getting close and we need to make a decision about this issue. We are going to descope most of the remaining issues to get the release...

I can see that source and lineno would be very useful for LSP. Unfortunately RF itself doesn't have that information available at the moment so that makes implementation a lot...