--- - branch: MAIN date: Mon May 1 09:47:32 UTC 2023 files: - new: '1.3' old: '1.2' path: pkgsrc/devel/py-typeguard/Makefile pathrev: pkgsrc/devel/py-typeguard/Makefile@1.3 type: modified - new: '1.2' old: '1.1' path: pkgsrc/devel/py-typeguard/PLIST pathrev: pkgsrc/devel/py-typeguard/PLIST@1.2 type: modified - new: '1.2' old: '1.1' path: pkgsrc/devel/py-typeguard/distinfo pathrev: pkgsrc/devel/py-typeguard/distinfo@1.2 type: modified id: 20230501T094732Z.df2525da690f72fed15e5ef3f0f6a4f50ea8a0c0 log: | py-typeguard: update to 3.0.2. **3.0.2** (2023-03-22) - Improved warnings by ensuring that they target user code and not Typeguard internal code - Fixed ``warn_on_error()`` not showing where the type violation actually occurred - Fixed local assignment to ``*args`` or ``**kwargs`` being type checked incorrectly - Fixed ``TypeError`` on ``check_type(..., None)`` - Fixed unpacking assignment not working with a starred variable (``x, *y = ...``) in the target tuple - Fixed variable multi-assignment (``a = b = c = ...``) being type checked incorrectly **3.0.1** (2023-03-16) - Improved the documentation - Fixed assignment unpacking (``a, b = ...``) being checked incorrectly - Fixed ``@typechecked`` attempting to instrument wrapper decorators such as ``@contextmanager`` when applied to a class - Fixed ``py.typed`` missing from the wheel when not building from a git checkout **3.0.0** (2023-03-15) - **BACKWARD INCOMPATIBLE** Dropped the ``argname``, ``memo``, ``globals`` and ``locals`` arguments from ``check_type()`` - **BACKWARD INCOMPATIBLE** Removed the ``check_argument_types()`` and ``check_return_type()`` functions (use ``@typechecked`` instead) - **BACKWARD INCOMPATIBLE** Moved ``install_import_hook`` to be directly importable from the ``typeguard`` module - **BACKWARD INCOMPATIBLE** Changed the checking of collections (list, set, dict, sequence, mapping) to only check the first item by default. To get the old behavior, set ``typeguard.config.collection_check_strategy`` to ``CollectionCheckStrategy.ALL_ITEMS`` - **BACKWARD INCOMPATIBLE** Type checking failures now raise ``typeguard.TypeCheckError`` instead of ``TypeError`` - Dropped Python 3.5 and 3.6 support - Dropped the deprecated profiler hook (``TypeChecker``) - Added a configuration system - Added support for custom type checking functions - Added support for PEP 604 union types (``X | Y``) on all Python versions - Added support for generic built-in collection types (``list[int]`` et al) on all Python versions - Added support for checking arbitrary ``Mapping`` types - Added support for the ``Self`` type - Added support for ``typing.Never`` (and ``typing_extensions.Never``) - Added support for ``Never`` and ``NoReturn`` in argument annotations - Added support for ``LiteralString`` - Added support for ``TypeGuard`` - Added support for the subclassable ``Any`` on Python 3.11 and ``typing_extensions`` - Added the possibility to have the import hook instrument all packages - Added the ``suppress_type_checks()`` context manager function for temporarily disabling type checks - Much improved error messages showing where the type check failed - Made it possible to apply ``@typechecked`` on top of ``@classmethod`` / ``@staticmethod`` (PR by jacobpbrugh) - Changed ``check_type()`` to return the passed value, so it can be used (to an extent) in place of ``typing.cast()``, but with run-time type checking - Replaced custom implementation of ``is_typeddict()`` with the implementation from ``typing_extensions`` v4.1.0 - Emit ``InstrumentationWarning`` instead of raising ``RuntimeError`` from the pytest plugin if modules in the target package have already been imported - Fixed ``TypeError`` when checking against ``TypedDict`` when the value has mixed types among the extra keys (PR by biolds) - Fixed incompatibility with ``typing_extensions`` v4.1+ on Python 3.10 (PR by David C.) - Fixed checking of ``Tuple[()]`` on Python 3.11 and ``tuple[()]`` on Python 3.9+ - Fixed integers 0 and 1 passing for ``Literal[False]`` and ``Literal[True]``, respectively - Fixed type checking of annotated variable positional and keyword arguments (``*args`` and ``**kwargs``) - Fixed checks against ``unittest.Mock`` and derivatives being done in the wrong place module: pkgsrc subject: 'CVS commit: pkgsrc/devel/py-typeguard' unixtime: '1682934452' user: wiz