Daniel Huppmann

Thanks for the suggestion @phackstock - this could be a nice way to get rid of the utils function `_escape_regexp()` within `pattern_match()` (for the non-regexp use case) , which seems...

This is used as a trial for filtering the index-query to the IIASA Database API, see #697

I reverted the previous PR in #699, because **fnmatch** does not natively support filtering lists, using the pyam function `pattern_match()` directly was an easier fix. **fnmatch** might still be a...

Having `set_meta()` chainable would imply that (in default mode) you create a full copy of a potentially very large object (the timeseries data) to make changes on a small object...

I think the best approach would be to have `KNOWN_FUNCS` as a recognized pyam module, then include it in the API docs, and cross-reference it from the methods-docstrings using intersphinx...

> Would KNOWN_FUNCS live in the API-reference? Yes, maybe as new "Utility" page...?

Thanks @Jihoon for creating this issue! Can you please attach the data (as csv) for a minimal example that reproduces this error? I.e., only the filtered data that you want...

@znicholls FYI because you implemented the logging tests...

The [pytest docs](https://docs.pytest.org/en/latest/reference.html#pytest.logging.LogCaptureFixture.at_level) for `caplog.at_level()` don't indicate that the test of the logger [here](https://github.com/IAMconsortium/pyam/blob/9761f0fd25c8106d16881d34828030bc1294553d/tests/test_logger.py#L29) should not work as before - but it seems (as of v6.0) to change the log-level...

thanks @znicholls for investigating and raising the issue with the pytest devs! Let's keep the dependency pinned for now and hope that they'll fix it in the not-too-distant future.