...to financially feed @leycec and his friendly @beartype.

Through your incredible outpouring of ongoing support, @beartype fuels your mission-critical Pythonic app stack with runtime type-checking so fast your devops engineers didn't even know it was happening – but it was.

Because @beartype already got there first.

Where We're Going, We Don't Need Roads Static Type Checking

2022 is the year of the tiger bear. ⇒ 🐻 🐅

2022 is the year @beartype tightens its bear hug on Python's QA landscape. Your stack needs it, so we bring it. Thanks entirely to your tremendous charity, @beartype gracefully scales with your explosive data pipeline, gargantuan profit margins, and supersized academic citations. Because @beartype delivers the hype even as it destroys all your bugs.

In 2022, Team @beartype heatedly unleashes:

• Deeper type-checking. We're going all-in on deep type-checking this year. With renewed attention to builtin container types (dict, set), core container ABCs (e.g., collections.abc.Container, collections.abc.Iterable), and pure-Python callables (e.g., collections.abc.Callable, collections.abc.Coroutine), @beartype will type-check everything. Because your data cares, we care.
• Linear- and logarithmic-time type-checks. By the fearsome wizardry of our new configuration API, beartype will type-check:
  • A logarithmic number of items of any container in O(log n) time for callables and classes you really trust.
  • All items of any container in O(n) time for callables and classes you really, REALLY trust.
• Magical import hooks. Type-check anyone's package (even those you don't own) with a single beartype_everything() call at the top of your root __init__.py. Don't believe us? We don't blame you. It doesn't exist yet – but it could. By the raw power of PEP 302-compliant import hooks, @beartype will type-check everything on your behalf without you needing to decorate every callable and class across your or anyone else's codebase. Because your RSI-wracked wrists care, we care.
• Readable structured documentation. It's not too much to ask, which is why you keep asking. That's why we're finally delivering good on our hollow promises, crossed 🤞, and endless ✋-waving. In the time-honoured tradition of Sphinx ➕ ReadTheDocs, @beartype will finally sport documentation that no longer embarrasses us both. Because our monolithic README.rst made your coworker cross-eyed, we care and apologetically feel bad.

Your generous assistance enables all these things. Enable us enable you enable us enable yo–RuntimeError: maximum recursion depth exceeded

Who Are You and Why Are You Begging for Money Outside Our Server Rack?

Helllllllo, beautiful downstream consumer.

Lead @beartype maintainer @leycec (Cecil Curry) and his crack team of ursine collaborators summon you to meet the balding middle-aged man behind the photoshopped GitHub avatar.

^{Lilium Stargazers conquer the summer garden like baldness conquered @leycec last year.}

^{You wouldn't believe the things these shades have seen.}

^{If I can't feel my face, then why does it feel so good?}

^{Goblin-mode monkey cat & man friend regret nothing.}

Thanks so much for bearing with us. As the many years and the versions churn, you don't just make the impossible plausible. You make the journey fun; you make the journey insightful; you make the journey necessary.

You mean the world. 🤗

        — @leycec