Cecil Curry

> Thankfully, github allows up to 2GB for each release file... **Rejoice!** We eating good. Bless you, Microsoft. 🤗 > And every patch that I have except the 1920 upscale...

**WOAH.** I *never* even knew that PEP 695 `type` aliases were subscriptable like that. Makes sense, though. More generics madness for our infinite queue of feature requests, huh? Sure. This...

**Resolved by e80f9b58db3e.** @beartype now offically supports PEP 695-compliant generic `type` aliases (which you asked for) as well as PEP 484- and 585-compliant subscripted generics (which you *didn't* ask for,...

Thanks for so much for the tremendous volunteerism, everybody. @beartype loves you guys! Okay. I admit. It probably seems like @beartype is ignoring you guys. It only *looks* like that,...

**Addendum:** Let's see here... > seems like it is quite easy to add a guard for having no keyword args in the function to be cached, perhaps you want to...

**Yup.** To [narcissistically quote my younger self from two weeks ago](https://github.com/beartype/beartype/discussions/559#discussioncomment-15020309): > *...heh.* You caught me out. I have no idea what I'm doing with `uv`. It's a beast. It's...

*...heh.* Thanks so much for the super-deep dive, @bitranox. You're totally right about the `uv` edge in continuous integration (CI) workflows. Even in local `tox` workflows, `pip` is unspeakably slow....

**Wondrous!** Finally, somebody is trying out `is_pep557_fields`. I'm so happy my emoji is crying. 😂 Tragically, `is_pep557_fields` is currently incompatible with PEP 563 (i.e., `from __future__ import annotations`). This is...

Oh, no worries whatsoever. This is an excellent feature request. Let's reopen this. It's actually a super-useful reminder for me to "Just get this done already!" Also, I love closing...