goodboy

@RonnyPfannschmidt what would be some other examples for alternative registry namespaces? I find building out a general API at least requires a couple examples. Maybe the filesystem-`conftest.py` listed `pytest_plugins` variables...

>Say my application is a concurrent application and the hook implementation is applied to a great amount of data, which means it would be executed thousands of times. @nnop this...

@RonnyPfannschmidt gotcha, thanks.

@rbdixon woo I actually really like this. Would you mind making a PR and some tests. We might need to think about how to handle py2 as well.

Hmm, though I like this cleanup I wonder if we should wait until #260 and #244 are discussed more. I'm wondering if we should be handling `Exception` vs. `BaseException` differently...

Was just thinking about this change again for some odd reason and was thinking maybe we shouldn't be catching and packing `BaseException` at all? The set of exceptions that derive...

> I haven't analyzed exactly where pytest relies on it, so it might be possible to adjust it not to rely on it. I feel like this might be somewhat...

Yeah the main thing that seems odd to me is catching any of these base exception types will likely have no value in result unboxing since they are all system...

Some other options to investigate: - [pytest-profiling](https://github.com/manahl/pytest-plugins/tree/master/pytest-profiling) - the [pytest benchmark scripts](https://github.com/pytest-dev/pytest/tree/master/bench)

There was recently [a post](https://mail.python.org/pipermail/pytest-dev/2018-November/004645.html) on the `pytest` mailing list about a new alternative bench-marking system as well.