[dependabot]

Updates the requirements on wrapt to permit the latest version.

Release notes

Sourced from wrapt's releases.

wrapt 2.5.2

Full release notes: https://wrapt.readthedocs.io/en/latest/changes.html#version-2-5-2

Install from PyPi (recommended):

pip install wrapt==2.5.2

PyPi uploads follow each GitHub release; if pip reports the version is unavailable, the matching PyPi upload may not have happened yet.

Pre-built wheels are provided for a range of Python versions and platforms (Linux x86_64/aarch64/riscv64, macOS x86_64 and arm64, Windows x86_64 and arm64, plus PyPy and free-threaded builds). The source distribution is also attached together with SHA256SUMS for verification.

Changelog

Sourced from wrapt's changelog.

Version 2.5.2

Bugs Fixed

• The special methods added to the class generated for an wrapt.AutoObjectProxy, and adjusted when __wrapped__ was reassigned, were determined by inspecting the wrapped object itself, rather than the type of the wrapped object. As special methods are only ever looked up on the type of an object, this gave the wrong result in several cases. When the wrapped object was a class, the special methods it defined for its instances were added to the proxy class, so a proxy for a class defining __set_name__() raised TypeError when assigned to an attribute in a class body, a proxy for a class defining __get__() was bound as a descriptor on attribute access, and a proxy for a class defining __await__() or __iter__() was reported as awaitable or iterable by inspect.isawaitable() and collections.abc checks, even though the class itself was not. Special methods provided by the metaclass of a wrapped class, such as __iter__(), were not added to the proxy class. When the wrapped object was an instance, instance attributes shadowing the dunder names were treated as special methods of the wrapped object, and special methods which a __dir__() method of the wrapped object did not report were missed. The special methods are now always determined from the type of the wrapped object, so a proxy behaves the same as the object it wraps. This also covers a wrapt.LazyObjectProxy whose factory returns an object, as resolving the wrapped object reassigns __wrapped__. With thanks to ybai08 for pull request [#361](https://github.com/GrahamDumpleton/wrapt/issues/361) <https://github.com/GrahamDumpleton/wrapt/pull/361>_ which identified the issue.

Version 2.5.1

Bugs Fixed

• A LazyObjectProxy created with an interface argument that declared a path-like type, such as os.PathLike or pathlib.Path, did not define the __fspath__() special method on the class it generated. Because os.fspath() looks up __fspath__() on the type of the object, passing such a proxy to os.fspath(), the builtin open() or other standard library functions accepting paths raised TypeError before the factory callable had been invoked to create the wrapped object. The __fspath__() special method is now added when the declared interface provides it, in the same way as is already done for the other special methods looked up on the type, so the first path conversion triggers creation of the wrapped object and succeeds. With thanks to Muneeb Sheikh for pull request [#360](https://github.com/GrahamDumpleton/wrapt/issues/360) <https://github.com/GrahamDumpleton/wrapt/pull/360>_.

... (truncated)

Commits

• c82d75d Merge branch 'hotfix/2.5.2'
• 522e8cc Pin the remaining CI jobs to ubuntu-24.04 so the whole pipeline uses the same...
• bdce62f Merge branch 'hotfix/2.5.2'
• 13218c6 Pin Linux CI test jobs to ubuntu-24.04 as ubuntu-latest moved to 26.04.
• c452d19 Merge branch 'release/2.5.2'
• c4b9a10 Drop the release candidate suffix for the 2.5.2 release.
• 6b4e844 Drop end of life PyPy 3.9 from the CI test matrix.
• 8dcd47a Determine auto proxy special methods from the type of the wrapped object.
• f72bbde Update to 2.5.2rc1.
• b521fe6 Merge tag '2.5.1' into develop
• See full diff in compare view