Releases · beartype/ipython-beartype

ipython-beartype 0.2.0 arises like the dread Lich King from that homebrew D&D campaign you just plowed through with your local area tabletop neckbeard group. You know what to do. The music may change, but the song remains the same:

pip install --upgrade ipython-beartype     # <-- unleash your inner QA

ipython-beartype 0.2.0 is gratefully brought to you by...

GitHub Sponsors: When You Befriend the Bear, You've got a Bear for Life

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 and Metrology. That's who.}

Let's get this pawful party started.

ipython-beartype 0.2.0: It Actually Works, Now

ipython-beartype 0.2.0 is a dramatic improvement over our first release a few months ago, which already seems like a lifetime ago. The exciting (yet boring) litany of changes includes:

@beartype ≥ 0.21.0 compatibility. Our initial ipython-beartype 0.1.0 release lacked support for newer @beartype releases, due to unsafely violating privacy encapsulation in the @beartype codebase. All new ipython-beartype releases should now be forward-compatible with all newer @beartype releases. Truly, ipython-beartype actually works now. The relief we feel is palpable, much like that pulsating vein on @leycec's forehead.
Automated release workflow. Like @beartype itself, ipython-beartype releases are now automated through our Good Ol' GitHub Actions-based workflow. This has knock-on effects, like:
- Tarballs. Our initial ipython-beartype 0.1.0 release lacked a source-based tarball. All new releases should now automatically provide both tarballs and wheels, much to the relief of humanity.
- PyPI Trusted Publishers. Our initial ipython-beartype 0.1.0 release lacked trust from the PyPI cheeseshop. All new releases should now automatically be marked as trusted. Thanks for no longer marking our suspicious releases as sketchy af, PyPI.
Test suite. Like @beartype itself, ipython-beartype now sports a pytest- and tox-backed test suite. Unlike @beartype itself, this test suite currently only consists of a single smoke test guaranteeing that ipython-beartype is at least importable by end users. It isn't much, but the bear takes whatever scraps well-meaning passerby are willing to feed it around here. 🐻

ipython-beartype 0.2.0: Built by Human Hands

ipython-beartype 0.2.0 would like to give a huge roar-out to these relentless GitHubbers, without whom ipython-beartype 0.2.0 would have sucked and basically not worked at all:

@tusharsadhwani (Tushar Sadhwani), the long-standing ipython-beartype and pytest-beartype maintainer. Tushar graciously postponed his super-fun Bay Area workcation to attend to super-not-fun project bureaucracy. You da GitHub Man, Tushar! 🤗
@ntjohnson1 (Nick), who authored pivotal PR #2, which improved so many things across the ipython-beartype codebase we cannot possibly list them all without passing out from keyboard heat stroke. Literally everything above is thanks to Nick. Thanks so much for your awesome volunteerism! You da GitHub Man too, Nick! 🥇

Bear Club: The Second Rule of Bear Club Is You Crush Bugs in Jupyter

@beartype high-fives the reclusive secret society of worldwide bear bros who might possibly care about this. You are the select few. The elect enlightened. You are:

@posita, @wesselb, @tusharsadhwani, @ntjohnson1, @bollwyvl, @jevinskie, @samyakbardiya, @pablovela5620