forked from pool/python-beartype
Dirk Mueller
05cf2fbf4a
* This minor release brings exhilarating support for PEP
673 (i.e., `typing.Self`) and PEP 675 (i.e.,
`typing.LiteralString`) as well as
substantially improved compatibility with PyPy.
* This release resolves a significant incompatibility
with PyPy, whose implementation of the `id()` builtin appears
to occasionally [read: non-deterministically] return object
identifiers that are negative integers. Specifically,
@beartype now guaranteeably generates valid parameter names
passed to type-checking wrapper functions regardless of the
sign of the `id()` of the values of those parameters. Doing
so resolves issue #232 kindly submitted by @jvesely (Jan
Vesely) who purportedly lives in or around an ancient pork
by-product that has calcified into stone -- which is quite
impressive, really. Stoneham: it's like Stonehenge, only
American and yummy in your tummy. Thanks so much for the
heads up, @jvesely.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-beartype?expand=0&rev=9
79 lines
3.8 KiB
Plaintext
79 lines
3.8 KiB
Plaintext
-------------------------------------------------------------------
|
||
Wed May 3 15:40:20 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||
|
||
- update to 0.14.0:
|
||
* This minor release brings exhilarating support for PEP
|
||
673 (i.e., `typing.Self`) and PEP 675 (i.e.,
|
||
`typing.LiteralString`) as well as
|
||
substantially improved compatibility with PyPy.
|
||
* This release resolves a significant incompatibility
|
||
with PyPy, whose implementation of the `id()` builtin appears
|
||
to occasionally [read: non-deterministically] return object
|
||
identifiers that are negative integers. Specifically,
|
||
@beartype now guaranteeably generates valid parameter names
|
||
passed to type-checking wrapper functions regardless of the
|
||
sign of the `id()` of the values of those parameters. Doing
|
||
so resolves issue #232 kindly submitted by @jvesely (Jan
|
||
Vesely) who purportedly lives in or around an ancient pork
|
||
by-product that has calcified into stone -- which is quite
|
||
impressive, really. Stoneham: it's like Stonehenge, only
|
||
American and yummy in your tummy. Thanks so much for the
|
||
heads up, @jvesely.
|
||
|
||
-------------------------------------------------------------------
|
||
Sun Apr 16 09:16:52 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||
|
||
- update to 0.13.1:
|
||
* The `test_pep561_mypy()` integration test validating that
|
||
@beartype passes all mypy-specific static runtime type-
|
||
checks
|
||
* **Pandera (pandas) type hints** (i.e., ad-hoc PEP-
|
||
noncompliant type hints validating pandas `DataFrame`
|
||
objects, produced by subscripting factories published by the
|
||
`pandera.typing` subpackage and validated *only* by user-
|
||
defined callables decorated by the ad-hoc PEP-noncompliant
|
||
`@pandera.check_types` runtime type-checking decorator),
|
||
resolving feature request #227 kindly submitted by
|
||
@ulfaslakprecis (Ulf Aslak) the Big Boss Typer. @beartype
|
||
now:
|
||
* Transparently supports pandera's PEP-noncompliant
|
||
`@pandera.check_types` decorator for deeply runtime type-
|
||
checking arbitrary pandas objects.
|
||
* *Always* performs a rudimentary `O(1)` `isinstance()`-based
|
||
type-check for each pandera type hint. Doing so substantially
|
||
improves usability in common use cases, including:
|
||
* Callables annotated by one or more pandera type hints that
|
||
are correctly decorated by @beartype but incorrectly *not*
|
||
decorated by the pandera-specific `@pandera.check_types`
|
||
decorator.
|
||
* (Data)classes annotated by one or more pandera type hints.
|
||
* Pandera type hints passed as the second argument to
|
||
statement-level @beartype type-checkers – including:
|
||
* **Pseudo-callable monkey-patching support.** `@beartype` now
|
||
supports **pseudo-callables** (i.e., otherwise uncallable
|
||
objects masquerading as callable by defining the `__call__()`
|
||
dunder method), resolving feature request #211 kindly
|
||
submitted by Google X typing guru @patrick-kidger (Patrick
|
||
Kidger). When passed a pseudo-callable whose `__call__()`
|
||
method is annotated by one or more type hints, `@beartype`
|
||
runtime type-checks that method in the standard way.
|
||
|
||
-------------------------------------------------------------------
|
||
Wed Jan 25 13:18:26 UTC 2023 - Daniel Garcia <daniel.garcia@suse.com>
|
||
|
||
- Disable test_beartype_in_sphinx, broken with sphinx 6.1.3
|
||
gh#beartype/beartype#209
|
||
- Update to version 0.12.0
|
||
Change log - https://github.com/beartype/beartype/releases
|
||
|
||
-------------------------------------------------------------------
|
||
Wed Oct 12 02:44:23 UTC 2022 - Yogalakshmi Arunachalam <yarunachalam@suse.com>
|
||
|
||
- Update to version 0.11.0
|
||
Change log - https://github.com/beartype/beartype/releases
|
||
|
||
-------------------------------------------------------------------
|
||
Thu May 5 06:14:45 UTC 2022 - Matej Cepl <mcepl@suse.com>
|
||
|
||
- Initial packaging effort for beartype 0.10.4.
|