Cecil Curry

**...woah.** Thanks for the superb heads-up, @gotmax23! As you can probably surmise from @beartype's continued stumbling towards the finish line, Python 3.14 support is highly non-trivial for runtime type-checkers like...

I apologize for blocking Fedora in general and your work specifically. I've triaged this as my immediate priority. Let us hope this means something. Thank you for being so understanding,...

**First milestone:** *done.* @beartype now officially supports PEP 649, en-route to fully supporting Python 3.14. This is shocking (yet appreciated) news. We are on-schedule to close this issue out within...

**Resolved by 1ea338d** – and in less than the predicted time, too! I must be dreaming. Slap me gently, somebody. Thanks for prodding me to do the hard work that...

**Superb!** Thanks for being so understanding. I'll endeavor to be more on the ball with Python 3.15 next year. Do my hollow promises mean anything, though? 🤔

**Superb!** Indeed, `typing.Annotated[...]` *should* solve almost everything. You'll probably still need to strip ANSI escape sequences like `[0m` from logged type-checking violation messages by disabling @beartype colourization: e.g., ```python #...

**Wondrousness!** Apologies for my *extreme* delay, too. I've been putting out raging fires all over the issue tracker for the last week. My excuses may be weak, but they're all...

**Urgh!** I briefly looked into adding official `typer` support to @beartype tonight. Sadly, it's infeasible from @beartype's perspective. I know, right? I'm sobbing over here. :sob: This is a core...

Actually, @beartype *can* do something. @beartype can loudly advise everybody to stop type-checking PEP-noncompliant `typer` commands with a new FAQ entry. @beartype users are strong. They can handle the truth!...

**...lol.** I am frequently wrong. We can admit that – some of us all too readily. Clearly, requiring users to manually hack around (arguable) deficiencies in @beartype is awful API...