pip runtime: bump beartype from 0.17.2 to 0.18.2

[dependabot]

Bumps beartype from 0.17.2 to 0.18.2.

Release notes

Sourced from beartype's releases.

Beartype 0.18.2: Now With Even Less Broky

Much like your neighbour's obese cat, even @​beartype 0.18.1 didn't quite work out as expected. This patch release temporarily squelches (i.e., silences) a low-level assert statement erroneously performed during @​beartype's dynamic code generation loop. Is this the end to the horror show that keeps on giving? Will the ill-fated @​beartype 0.18.x release cycle finally pass muster and stop violating the world? Tune in next time as @​leycec clutches his chest in agony live on GitHub.

Obligatory awesome peeps!

GitHub Sponsors: They Scratch the Bear's Back. Now, The Bear Scratches Back.

This release comes courtesy these proud GitHub Sponsors, without whom @​leycec's cats would currently be eating grasshoppers:

• @​sesco-llc (SESCO Enterprises), "The Power of Innovation in Trading": this inspires me to get out of the house and do something https://sescollc.com
• @​DylanModesitt (Dylan Modesitt), quantitative strategies energy trading associate: ...wikipedia, don't fail me now! https://dylanmodesitt.com

Thanks so much, masters of fintech.

The Masters of Fintech. That's who.

Beartype 0.18.1: Now With Less Broky

Much like your neighbour's obese cat, @​beartype 0.18.0 didn't quite work out as expected. This patch release temporarily reverts default value type-checking (i.e., type-checking of default values of optional parameters annotated by type hints accepted by @beartype-decorated callables), restoring sanity to the downstream community of @​beartype consumers.

Although desirable, this functionality is also a lot more nuanced than @​leycec previously assumed -- resulting in @​leycec clutching his bald head as if he still had something to clutch there. Since improving this functionality to be robust against breakage is non-trivial, the proper solution is to temporarily disable that functionality. Thus, we cry.

Obligatory awesome peeps!

GitHub Sponsors: They Scratch the Bear's Back. Now, The Bear Scratches Back.

This release comes courtesy these proud GitHub Sponsors, without whom @​leycec's cats would currently be eating grasshoppers:

• @​sesco-llc (SESCO Enterprises), "The Power of Innovation in Trading": this inspires me to get out of the house and do something https://sescollc.com
• @​DylanModesitt (Dylan Modesitt), quantitative strategies energy trading associate: ...wikipedia, don't fail me now! https://dylanmodesitt.com

Thanks so much, masters of fintech.

The Masters of Fintech. That's who.

Beartype 0.18.0: Dictionaries and Defaults at the Event Horizon of the Typing Hole

Beartype 0.18.0 whimsically gyrates around in balloon pants while chanting: "Can't touch this."

...even the token bald man in a smoking post-apocalyptic wasteland doesn't know

It's kinda creepy, honestly – and it's really getting on your nerves. Yes, we get it. You think you're hot junk, @​beartype 0.18.0! Yet you can't help but admire the sweat that coats its body. Beartype 0.18.0 worked out for this release. It's buff now. It's tough now. It does things now. It does things you thought it did five years ago now. Beartype 0.18.0 finally caught up to your expectations. It even tried to exceed them. It didn't, of course. It couldn't. It's only a bear. It rarely bathes. And, anyway, your expectations were unreasonable.

But... it almost did. Prepare to have your expectations almost exceeded:

... (truncated)

Commits

• 5216017 Beartype 0.18.2: Now With Even Less Broky
• de3f94d Obscure code generation assertion squelched.
• a458668 Beartype 0.18.2 started.
• acfcaef Beartype 0.18.1: Now With Less Broky
• 7b4976a Parameter default type-checking reversion.
• cdccff8 Beartype 0.18.1 started.
• af99dfe Beartype 0.18.0: Dictionaries and Defaults at the Event Horizon of the Typing...
• 874776a beartype.door.is_bearable() + PEP 647.
• 0fccdb4 Parameter default type-checking x 4.
• 3926b09 beartype.claw + typed keyword-only callables.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cofiem]

@dependabot merge