[GH PR #28] chore(deps): bump wrapt from 2.2.2 to 2.3.0 #2

Merged
redeuxx merged 2 commits from github-pr-28 into main 2026-08-01 01:00:31 -05:00
Owner

Bumps wrapt from 2.2.2 to 2.3.0.

Release notes

Sourced from wrapt's releases.

wrapt 2.3.0

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

Install from PyPi (recommended):

pip install wrapt==2.3.0

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.3.0rc2

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

May be installable from PyPi:

pip install wrapt==2.3.0rc2

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.3.0rc2.tar.gz
cd wrapt-2.3.0rc2
pip install .

SHA256SUMS is attached for verification of the archives.

wrapt 2.3.0rc1

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

May be installable from PyPi:

pip install wrapt==2.3.0rc1

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.3.0rc1.tar.gz

... (truncated)

Changelog

Sourced from wrapt's changelog.

Version 2.3.0

New Features

  • The __trunc__(), __floor__() and __ceil__() special methods are now implemented by object proxies, delegating to math.trunc(), math.floor() and math.ceil() applied to the wrapped object. As with other special methods, these are only looked up on the class type and not the instance, so they cannot rely on the __getattr__() fallback of the proxy and must be implemented explicitly. Previously calling math.trunc() on an object proxy raised TypeError. These special methods sit somewhat outside the core Python object model in that they are not used by any builtin operators, with the math module being their only consumer. They are however documented as part of the Python data model and the math module is a key module in the standard library, so supporting them is warranted, in the same way as the existing support for __round__(), which is consumed by the round() builtin. Note that although math.floor() and math.ceil() previously appeared to work when used on an object proxy, they were silently falling back to converting the proxy using __float__(). If the wrapped object provided its own __floor__() or __ceil__() special methods these were ignored and the result could differ from that when the wrapped object was used directly. These now yield the same result as using the wrapped object directly. With thanks to Vincent Gao for pull request [#344](https://github.com/GrahamDumpleton/wrapt/issues/344) <https://github.com/GrahamDumpleton/wrapt/pull/344>_.

  • The __fspath__() special method of the os.PathLike protocol has been added to the set of dunder methods which AutoObjectProxy detects on the wrapped object and adds to the class it generates, so a proxy it creates around a path-like object can now be used with os.fspath(), the builtin open() and other standard library functions accepting paths. Note that __fspath__() is deliberately not implemented by the base object proxy, since its presence on the proxy type would cause every proxy to be classified as path-like by code branching on isinstance(obj, os.PathLike). Also be aware that AutoObjectProxy creates a new class for every proxy instance, so it should not be used to wrap path-like objects in large numbers due to the memory overhead. For high-frequency use define a custom proxy class which adds an explicit __fspath__() method instead. See the section on wrapping path-like objects in the known issues documentation for more details.

Features Changed

  • The type stubs have been aligned with the runtime behaviour of the code and are now verified by stubtest against both the C extension and pure Python implementations. If using a type checker there are a couple of changes in what will be accepted which may be noticed. The

... (truncated)

Commits
  • 95d5d01 Merge branch 'release/2.3.0'
  • de09467 Update to 2.3.0 for final release.
  • f2f807e Update to 2.3.0rc2.
  • 4f6223e Acknowledge reporter in bytes() bug fix change log entry.
  • 783d058 Extend tests for bytes() conversion of object proxies.
  • 300d23d Merge pull request #345 from Sanjays2402/fix/bytes-proxy-int
  • 6cf6962 Make bytes() on a proxy match bytes() on the wrapped object
  • 58557a7 Update to 2.3.0rc1.
  • 2fe9961 Document buffer protocol behaviour of object proxies.
  • 818191b Force and verify C extension build in test-stubtest recipe.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Mirrored from https://github.com/redeuxx/whitespace/pull/28

Bumps [wrapt](https://github.com/GrahamDumpleton/wrapt) from 2.2.2 to 2.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/GrahamDumpleton/wrapt/releases">wrapt's releases</a>.</em></p> <blockquote> <h2>wrapt 2.3.0</h2> <p>Full release notes: <a href="https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0">https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0</a></p> <p>Install from PyPi (recommended):</p> <pre><code>pip install wrapt==2.3.0 </code></pre> <p>PyPi uploads follow each GitHub release; if <code>pip</code> reports the version is unavailable, the matching PyPi upload may not have happened yet.</p> <p>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 <code>SHA256SUMS</code> for verification.</p> <h2>wrapt 2.3.0rc2</h2> <p>Release candidate. Release notes for the upcoming 2.3.0 final (work in progress): <a href="https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0">https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0</a></p> <p>May be installable from PyPi:</p> <pre><code>pip install wrapt==2.3.0rc2 </code></pre> <p>If <code>pip</code> 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:</p> <pre><code>tar xf wrapt-2.3.0rc2.tar.gz cd wrapt-2.3.0rc2 pip install . </code></pre> <p><code>SHA256SUMS</code> is attached for verification of the archives.</p> <h2>wrapt 2.3.0rc1</h2> <p>Release candidate. Release notes for the upcoming 2.3.0 final (work in progress): <a href="https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0">https://wrapt.readthedocs.io/en/latest/changes.html#version-2-3-0</a></p> <p>May be installable from PyPi:</p> <pre><code>pip install wrapt==2.3.0rc1 </code></pre> <p>If <code>pip</code> 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:</p> <pre><code>tar xf wrapt-2.3.0rc1.tar.gz </code></pre> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/GrahamDumpleton/wrapt/blob/develop/docs/changes.rst">wrapt's changelog</a>.</em></p> <blockquote> <h2>Version 2.3.0</h2> <p><strong>New Features</strong></p> <ul> <li> <p>The <code>__trunc__()</code>, <code>__floor__()</code> and <code>__ceil__()</code> special methods are now implemented by object proxies, delegating to <code>math.trunc()</code>, <code>math.floor()</code> and <code>math.ceil()</code> applied to the wrapped object. As with other special methods, these are only looked up on the class type and not the instance, so they cannot rely on the <code>__getattr__()</code> fallback of the proxy and must be implemented explicitly. Previously calling <code>math.trunc()</code> on an object proxy raised <code>TypeError</code>. These special methods sit somewhat outside the core Python object model in that they are not used by any builtin operators, with the <code>math</code> module being their only consumer. They are however documented as part of the Python data model and the <code>math</code> module is a key module in the standard library, so supporting them is warranted, in the same way as the existing support for <code>__round__()</code>, which is consumed by the <code>round()</code> builtin. Note that although <code>math.floor()</code> and <code>math.ceil()</code> previously appeared to work when used on an object proxy, they were silently falling back to converting the proxy using <code>__float__()</code>. If the wrapped object provided its own <code>__floor__()</code> or <code>__ceil__()</code> special methods these were ignored and the result could differ from that when the wrapped object was used directly. These now yield the same result as using the wrapped object directly. With thanks to Vincent Gao for <code>pull request [#344](https://github.com/GrahamDumpleton/wrapt/issues/344) &lt;https://github.com/GrahamDumpleton/wrapt/pull/344&gt;</code>_.</p> </li> <li> <p>The <code>__fspath__()</code> special method of the <code>os.PathLike</code> protocol has been added to the set of dunder methods which <code>AutoObjectProxy</code> detects on the wrapped object and adds to the class it generates, so a proxy it creates around a path-like object can now be used with <code>os.fspath()</code>, the builtin <code>open()</code> and other standard library functions accepting paths. Note that <code>__fspath__()</code> is deliberately not implemented by the base object proxy, since its presence on the proxy type would cause every proxy to be classified as path-like by code branching on <code>isinstance(obj, os.PathLike)</code>. Also be aware that <code>AutoObjectProxy</code> creates a new class for every proxy instance, so it should not be used to wrap path-like objects in large numbers due to the memory overhead. For high-frequency use define a custom proxy class which adds an explicit <code>__fspath__()</code> method instead. See the section on wrapping path-like objects in the known issues documentation for more details.</p> </li> </ul> <p><strong>Features Changed</strong></p> <ul> <li>The type stubs have been aligned with the runtime behaviour of the code and are now verified by <code>stubtest</code> against both the C extension and pure Python implementations. If using a type checker there are a couple of changes in what will be accepted which may be noticed. The</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/95d5d01bd671186000c02e1d0f6806a4d7c5d217"><code>95d5d01</code></a> Merge branch 'release/2.3.0'</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/de094674f4d5e59b1b69c3b042ecc9b0eac729e7"><code>de09467</code></a> Update to 2.3.0 for final release.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/f2f807e002e6fab134cb7599b34b93cadc900bf1"><code>f2f807e</code></a> Update to 2.3.0rc2.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/4f6223ef946941e68352752dee1815bb2cb6ec9c"><code>4f6223e</code></a> Acknowledge reporter in bytes() bug fix change log entry.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/783d05877279e51d288466c0c0b37487c2034cf2"><code>783d058</code></a> Extend tests for bytes() conversion of object proxies.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/300d23d406ff929d169663d8f98347271add017d"><code>300d23d</code></a> Merge pull request <a href="https://redirect.github.com/GrahamDumpleton/wrapt/issues/345">#345</a> from Sanjays2402/fix/bytes-proxy-int</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/6cf696233e4d777cda88c6ee06053bf71f73a445"><code>6cf6962</code></a> Make bytes() on a proxy match bytes() on the wrapped object</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/58557a7cf87e325db675c9dfdf218600bec77daa"><code>58557a7</code></a> Update to 2.3.0rc1.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/2fe996189f298f7951aef75e1b63a9a585f1cff3"><code>2fe9961</code></a> Document buffer protocol behaviour of object proxies.</li> <li><a href="https://github.com/GrahamDumpleton/wrapt/commit/818191bef9075a07eea1092446123d2fdc5c6af6"><code>818191b</code></a> Force and verify C extension build in test-stubtest recipe.</li> <li>Additional commits viewable in <a href="https://github.com/GrahamDumpleton/wrapt/compare/2.2.2...2.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=wrapt&package-manager=pip&previous-version=2.2.2&new-version=2.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Mirrored from https://github.com/redeuxx/whitespace/pull/28
Bumps [wrapt](https://github.com/GrahamDumpleton/wrapt) from 2.2.2 to 2.3.0.
- [Release notes](https://github.com/GrahamDumpleton/wrapt/releases)
- [Changelog](https://github.com/GrahamDumpleton/wrapt/blob/develop/docs/changes.rst)
- [Commits](https://github.com/GrahamDumpleton/wrapt/compare/2.2.2...2.3.0)

---
updated-dependencies:
- dependency-name: wrapt
  dependency-version: 2.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
redeuxx/whitespace!2
No description provided.