[dependabot]

Bumps wrapt from 2.1.2 to 2.5.1.

Release notes

Sourced from wrapt's releases.

wrapt 2.5.1

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

Install from PyPi (recommended):

pip install wrapt==2.5.1

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.

wrapt 2.5.1rc1

Release candidate. Release notes for the upcoming 2.5.1 final (work in progress): https://wrapt.readthedocs.io/en/latest/changes.html#version-2-5-1

May be installable from PyPi:

pip install wrapt==2.5.1rc1

If pip reports the version is unavailable, this candidate either has not been uploaded yet or is not being published to PyPi. Use the attached wheels or build from the source distribution instead:

tar xf wrapt-2.5.1rc1.tar.gz
cd wrapt-2.5.1rc1
pip install .

SHA256SUMS is attached for verification of the archives.

wrapt 2.5.1.dev1

Development snapshot. Not normally published to PyPi (occasionally uploaded to exercise the release pipeline).

Release notes for the upcoming 2.5.1 final (work in progress): https://wrapt.readthedocs.io/en/latest/changes.html#version-2-5-1

Platform wheels and the source distribution are attached. To test against your Python install, either grab a matching wheel or build from the source distribution:

pip install wrapt-2.5.1.dev1-<python>-<abi>-<platform>.whl

or

... (truncated)

Changelog

Sourced from wrapt's changelog.

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>_.

• A callback passed to wrapt.WeakFunctionProxy which was callable but evaluated as false, such as an event emitter object which reports its number of subscribers via __len__() and is empty when first created, was passed the underlying weak reference object instead of the proxy when the wrapped function expired. Where the wrapped function was a bound method, such a callback could also be called twice, once each when the instance and the function expired. Only None is now treated as meaning no callback was supplied, which mirrors the behaviour of weakref.ref() and weakref.proxy() in the standard library, so these callbacks now receive the proxy and are called only once, as for any other callback. With thanks to Huanyi Xie for pull request [#359](https://github.com/GrahamDumpleton/wrapt/issues/359) <https://github.com/GrahamDumpleton/wrapt/pull/359>_.

• A wrapt.AdapterFactory instance passed as the adapter argument to wrapt.decorator was ignored, and so never called, if the instance evaluated as false, such as when the factory class defined __bool__() or __len__(). The decorated function then retained its original signature instead of that produced by the factory. Whether an adapter factory was supplied is now determined by type before the truth value of the adapter is considered, so such factories are always called. As a consequence of this change a factory can now also return None, or any other false value, to indicate that no adapter should be used for a particular function, where previously this failed with an obscure error. With thanks to Luochenchen for pull request [#358](https://github.com/GrahamDumpleton/wrapt/issues/358) <https://github.com/GrahamDumpleton/wrapt/pull/358>_ which identified the issue.

Version 2.5.0

New Features

... (truncated)

Commits

• dbbb21f Merge branch 'release/2.5.1'
• 95e2afb Drop the release candidate suffix for the 2.5.1 release.
• 1ed68ca Update to 2.5.1rc1.
• 77e826d Recognise adapter factories by type so one which evaluates as false is not ig...
• 13efe63 Move change note for PR #359 under 2.5.1 and add clarifying comments.
• 6ba6048 Reorder fspath handling in lazy proxy and add change note for PR #360.
• 5e97e2d Update to 2.5.1.dev1.
• e9d491c Merge pull request #359 from xiehuanyi/fix-falsey-weak-proxy-callbacks
• 0d6c935 Merge pull request #360 from muneikh/fix-lazy-pathlike-interface
• de574aa Honor the declared pathlike interface in lazy proxies
• Additional commits viewable in compare view

[BigSpaceships]

@dependabot rebase