Cecil Curry

**Just hit this.** In my case, [I'm packaging `dbus_next` for Gentoo Linux at my third-party overlay](https://github.com/leycec/raiagent). We prefer to locally run tests on installation for obvious reasons, because `tests passing...

**Affirmative.** Would it also be feasible to gracefully `@pytest.mark.skipif(..., reason='Non-portable dbus test.')` the relevant integration tests away, in that case? Tests that can only reliably run within a unique non-portable...

_oh._ I see from that #20 that this feature request may have been overly optimistic: > It is difficult to add same behavior for Spelunker.vim, because **it does not parse...

*@beartype lead joins the chat.* Thanks so much for pinging me on, @tlambert03! We should now mention that @tlambert03 single-handedly architected our [entire `beartype.door` API](https://github.com/beartype/beartype#beartype-object-oriented-api) via a gauntlet of gruesome...

> some sort of plug-in or hooking mechanism You ask for much, misty mountain gorilla. I actually have a `FIXME:` comment to myself buried somewhere within the @beartype codebase begging...

**Fascinating feature request intensifies.** Thanks so much for pinging me into the fray, @patrick-kidger. Exactly as you suspect, no actively maintained runtime type-checker *that I know of* currently performs static...

**Agh!** I should be more explicit in my jargon, especially when slinging around suspicious phrases like "destroying runtime performance." So... > Just to clarify on "destroying runtime performance", do you...

**Extremely impressive.** `@awfutils.typecheck` is the first practical attempt I've seen at performing static type-checking at runtime. Take my thunderous clapping! :clap: :clap: :clap: Your current approach is outrageously useful, but...

**Necrobump.** We're seeing the exact same behaviour as @nschloe in [beartype/beartype](https://github.com/beartype/beartype), where `pytest-cov` successfully generates `coverage.xml` files under pytest but *not* tox. `pytest-cov` proudly *claims* that it's generating `coverage.xml` files...

> It is generating it, it's just that it's not placing it in the project root, because you have used `changedir = {envtmpdir}`... Fascinating! So *that's* it's final destination. Thanks...