Victor Maryama

@RonnyPfannschmidt nice to hear that! Merging repeated calls inside a parent is problematic because it does not capture the fact that, for instance, pytest__runtest_makereport runs three times, after setup, call,...

Just stumbled upon this presentation which has a similar tree view of the hooks (including annotations where there is repetitions): http://devork.be/talks/pluggy/pluggy.html Do you guys know him? Should we contact him...

I updated the script to use a list of hooks to merge or to exclude from merging, but other than that I am out of ideas on the best way...

Hi! So this stopped so far because I couldn't figure out: - best way to treat repeated hook calls. Some of them we would like to keep (makereport after each...

@31nm create (in the same folder you call pyinstaller) a file called `hook-pygal.py` with the following contents: ``` from PyInstaller.utils.hooks import collect_data_files datas = collect_data_files('pygal') ``` then add the following...

@mcarans using assume as a context manager retains the pytest generated explanations, as you will still be having the `assert` keyword and those will naturally be rewritten by pytest.

Yes!

As of today, anything that is not `AssertionError` or subclass will not be caught by `assume` and will fail the test instantly, without executing further code (e.g. other assumes following...

It would make sense to merge this plugin to pytest core as a "soft assertion" feature and indeed have this in the assertion rewrite module.

One possible solution is to implement both hook calls `pytest_runtest_call` and `pytest_pyfunc_call` which defer to a meta function containing all the logic (after the yield). `pytest_pyfunc_call` would always call the...