Paweł

Yeah, I agree - I think that the dumbest option will be the best in this case. I wouldn't worry about parent/children/multi-process combinations and just simply report time spent when...

I know it's been a while, but I'm going to respond to let you decide/close/resolve the issue as appropriate. Agreed - if I wanted to really dive into performance details,...

1. Agreed and understood, I'm only upgrading to Eliot-0.6 now - no urgency required. 2. Yeah, it occurred to me too when I posted the previous message. But, in practice,...

Well, abridged action wouldn't really help us - we literally don't care about 80%+ of the requests, so even abridged start+end would result in a lot of clutter. It could...

The use case was kind of an on-line store. As long as people are browsing through products, we don't really want to log anything - we're indexing ngingx access logs,...

Sorry, I don't know how to solve your use case. Also, I don't see how a ring-buffer could help :/ I'm not sure if both of our cases can we...

+1 on this. I'm currently writing tests that look like: ``` python @pytest.fixture def my_fixture(): return 'something' @pytest.fixture def another_fixture(my_fixture): return {'my_key': my_fixture} def yet_another_fixture(): return {'my_key': None} @pytest.mark.parametrize('arg1, arg2',...

@RonnyPfannschmidt I know - and that's why I'd like to be able to use fixtures in `parametrize`? And that would be awesome. My example is wrong, but it follows the...

ok, I don't understand python. If the below works: ``` python @pytest.fixture def my_fixture return 1 def test_me(my_fixture): assert 1 == my_fixture ``` wouldn't the below be simpler? And an...

yeah, I read the proposal. I'm just surprised you're going with `pytest.fixture_request(' default_context')`it feels very verbose? after all, ``` python @pytest.fixture def my_fixture return 1 def test_me(my_fixture): assert 1 ==...