[pull] master from aio-libs:master - #746
Merged
Merged
Conversation
Bumps [pydantic](https://github.com/pydantic/pydantic) from 2.13.4 to 2.13.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/releases">pydantic's releases</a>.</em></p> <blockquote> <h2>v2.13.5 (2026-08-28)</h2> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Allow reuse of validators when plugins are set by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13535">#13535</a></li> <li>Fix missing GC traversal on some <code>pydantic-core</code> struct fields by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13624">#13624</a></li> <li>Fix missing GC traversal in <code>pydantic-core</code> for <code>GeneralFieldsSerializer</code> by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13629">#13629</a></li> <li>Count validated model fields once in smart unions by <a href="https://github.com/tamird"><code>@tamird</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13731">#13731</a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/blob/v2.13.5/HISTORY.md">pydantic's changelog</a>.</em></p> <blockquote> <h2>v2.13.5 (2026-08-28)</h2> <p><a href="https://github.com/pydantic/pydantic/releases/tag/v2.13.5">GitHub release</a></p> <h3>What's Changed</h3> <h4>Fixes</h4> <ul> <li>Allow reuse of validators when plugins are set by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13535">#13535</a></li> <li>Fix missing GC traversal on some <code>pydantic-core</code> struct fields by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13624">#13624</a></li> <li>Fix missing GC traversal in <code>pydantic-core</code> for <code>GeneralFieldsSerializer</code> by <a href="https://github.com/Viicos"><code>@Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13629">#13629</a></li> <li>Count validated model fields once in smart unions by <a href="https://github.com/tamird"><code>@tamird</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/13731">#13731</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pydantic/pydantic/commit/001dea020e0809844e5b17666432c9135a976f46"><code>001dea0</code></a> Bump <code>pypa/gh-action-pypi-publish</code> action to v1.14.2</li> <li><a href="https://github.com/pydantic/pydantic/commit/558379fee957fad25858e33596146c72d5674843"><code>558379f</code></a> Bump twine to v7.0.0</li> <li><a href="https://github.com/pydantic/pydantic/commit/2cfd5d3d2ae721ea882c045f83b7f7a4003aab01"><code>2cfd5d3</code></a> Do not check for docs build</li> <li><a href="https://github.com/pydantic/pydantic/commit/a735bee5c64e1fe50785c376adaf1275e752b8ac"><code>a735bee</code></a> Fix more Clippy lints</li> <li><a href="https://github.com/pydantic/pydantic/commit/7eed4a16b87afaced4d0eafae230453de3410d64"><code>7eed4a1</code></a> Fix Clippy 0.1.95 warnings</li> <li><a href="https://github.com/pydantic/pydantic/commit/b353bbb20a4989b4c033e2be2b4a40d36178b16a"><code>b353bbb</code></a> Prepare release v2.13.5</li> <li><a href="https://github.com/pydantic/pydantic/commit/63d2cccd6e760da6bbc7fe81a53cb2bde3768f5e"><code>63d2ccc</code></a> Count validated model fields once in smart unions</li> <li><a href="https://github.com/pydantic/pydantic/commit/a53ec2ed342fda4e6aa3684399d04ea57be9a6e4"><code>a53ec2e</code></a> Speed up PyPy CI tests</li> <li><a href="https://github.com/pydantic/pydantic/commit/d65e0f96e890ca82f4b66a15d5b3bd65af2c661c"><code>d65e0f9</code></a> Workaround circular import error in Mypy</li> <li><a href="https://github.com/pydantic/pydantic/commit/47a6dbf8ad6216211bd0df6ec5c2c6c6ed905b72"><code>47a6dbf</code></a> Fix missing GC traversal in <code>pydantic-core</code> for <code>GeneralFieldsSerializer</code></li> <li>Additional commits viewable in <a href="https://github.com/pydantic/pydantic/compare/v2.13.4...v2.13.5">compare view</a></li> </ul> </details> <br /> [](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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [coverage](https://github.com/coveragepy/coveragepy) from 7.15.4 to 7.16.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/coveragepy/coveragepy/releases">coverage's releases</a>.</em></p> <blockquote> <h2>7.16.0</h2> <h2>Version 7.16.0 — 2026-08-28</h2> <ul> <li>When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define <code>[paths]</code> configuration to combine data across operating systems. Fixes <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2266">issue 2266</a>.</li> <li>The <a href="https://coverage.readthedocs.io/en/latest/api_coverage.html#coverage.Coverage.switch_context">Coverage.switch_context()</a> method now returns the previous context.</li> <li>Fix: previously, a <code>[paths]</code> pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2268">pull 2268</a>.</li> <li>Fixes to validation of options and configuration settings: <ul> <li>Negative precision settings now always cause useful error messages (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2261">pull 2261</a>).</li> <li>An invalid regex in the <code>--contexts</code> option (or the <code>[report] contexts</code> setting) reported a confusing “Couldn’t use data file …: user-defined function raised exception” error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2262">pull 2262</a>).</li> <li>Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren’t strings (like <code>omit</code>, <code>exclude_lines</code>, or a <code>[paths]</code> entry), file settings like <code>data_file</code>, and any wrong-typed value in the <code>[paths]</code> section (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2263">pull 2263</a>).</li> <li><code>coverage run</code> refuses run-affecting command-line options like <code>--branch</code> alongside <code>--concurrency=multiprocessing</code>, since they can’t reach the subprocesses. The check only recognized <code>multiprocessing</code> as the entire option value, so <code>--concurrency=multiprocessing,thread</code> slipped through and failed later with “Can’t combine statement coverage data with branch data”. Each named concurrency library is now properly considered (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2270">pull 2270</a>).</li> </ul> </li> <li>Fix: <code>coverage annotate -d DIR</code> raised an <code>AssertionError</code> if any measured file had an extension other than <code>.py</code>, such as a <code>.pyw</code> file on Windows. The original extension is now restored on the annotated copy (<a href="https://redirect.github.com/coveragepy/coveragepy/pull/2265">pull 2265</a>).</li> </ul> <p>:arrow_right: PyPI page: <a href="https://pypi.org/project/coverage/7.16.0">coverage 7.16.0</a>. :arrow_right: To install: <code>python3 -m pip install coverage==7.16.0</code></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst">coverage's changelog</a>.</em></p> <blockquote> <h2>Version 7.16.0 — 2026-08-28</h2> <ul> <li> <p>When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define <code>[paths]</code> configuration to combine data across operating systems. Fixes <code>issue 2266</code>_.</p> </li> <li> <p>The :meth:<code>.Coverage.switch_context</code> method now returns the previous context.</p> </li> <li> <p>Fix: previously, a <code>[paths]</code> pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in <code>pull 2268</code>_.</p> </li> <li> <p>Fixes to validation of options and configuration settings:</p> <ul> <li> <p>Negative precision settings now always cause useful error messages (<code>pull 2261</code>_).</p> </li> <li> <p>An invalid regex in the <code>--contexts</code> option (or the <code>[report] contexts</code> setting) reported a confusing "Couldn't use data file ...: user-defined function raised exception" error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (<code>pull 2262</code>_).</p> </li> <li> <p>Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren't strings (like <code>omit</code>, <code>exclude_lines</code>, or a <code>[paths]</code> entry), file settings like <code>data_file</code>, and any wrong-typed value in the <code>[paths]</code> section (<code>pull 2263</code>_).</p> </li> <li> <p><code>coverage run</code> refuses run-affecting command-line options like <code>--branch</code> alongside <code>--concurrency=multiprocessing</code>, since they can't reach the subprocesses. The check only recognized <code>multiprocessing</code> as the entire option value, so <code>--concurrency=multiprocessing,thread</code> slipped through and failed later with "Can't combine statement coverage data with branch data". Each named concurrency library is now properly considered (<code>pull 2270</code>_).</p> </li> </ul> </li> <li> <p>Fix: <code>coverage annotate -d DIR</code> raised an <code>AssertionError</code> if any measured file had an extension other than <code>.py</code>, such as a <code>.pyw</code> file on Windows. The original extension is now restored on the annotated copy (<code>pull 2265</code>_).</p> </li> </ul> <p>.. _pull 2261: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2261">coveragepy/coveragepy#2261</a> .. _pull 2262: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2262">coveragepy/coveragepy#2262</a> .. _pull 2263: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2263">coveragepy/coveragepy#2263</a> .. _pull 2265: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2265">coveragepy/coveragepy#2265</a> .. _issue 2266: <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2266">coveragepy/coveragepy#2266</a> .. _pull 2268: <a href="https://redirect.github.com/coveragepy/coveragepy/pull/2268">coveragepy/coveragepy#2268</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/coveragepy/coveragepy/commit/3e9fc1653ef31089d02eb7618b9d9ac9414378fc"><code>3e9fc16</code></a> docs: prep for 7.16.0</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/38be8d13afee6b6525492fc375c739cdfb675e9b"><code>38be8d1</code></a> build: control check-manifest explicitly</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/8eb1266ead5c6d356d3437637a509ff86b566253"><code>8eb1266</code></a> docs(build): no longer commit sample_html</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/1a8b3fa57d56bb70bad62c93d224c18a0fbaae6f"><code>1a8b3fa</code></a> docs: remove sample_html</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/aeaa79b812d1bc637ebb5582ab12c076e192c87e"><code>aeaa79b</code></a> docs: linklint is now sphinx-linklint</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/d5eaf3f6d38f58746bc69e87e64c0b0277a9077d"><code>d5eaf3f</code></a> test: a branchless way to re-add extensions</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/57e52fd431cecc1ca03de2c5b1288e0b330c2ef4"><code>57e52fd</code></a> docs: adjust CHANGES for <a href="https://redirect.github.com/coveragepy/coveragepy/issues/2270">#2270</a></li> <li><a href="https://github.com/coveragepy/coveragepy/commit/b9d304d77f7ce3d55df3a46339dbc56d1f49df58"><code>b9d304d</code></a> fix: check for multiprocessing in a --concurrency list (<a href="https://redirect.github.com/coveragepy/coveragepy/issues/2270">#2270</a>)</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/a6ef9284afbc7d1f392821864b64ddbda0051fc5"><code>a6ef928</code></a> chore: make upgrade</li> <li><a href="https://github.com/coveragepy/coveragepy/commit/070461fcfde0437b5b778c2c2a72e433a0a391aa"><code>070461f</code></a> chore: bump the action-dependencies group with 4 updates (<a href="https://redirect.github.com/coveragepy/coveragepy/issues/2271">#2271</a>)</li> <li>Additional commits viewable in <a href="https://github.com/coveragepy/coveragepy/compare/7.15.4...7.16.0">compare view</a></li> </ul> </details> <br /> [](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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [python-discovery](https://github.com/tox-dev/python-discovery) from 1.5.3 to 1.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/python-discovery/releases">python-discovery's releases</a>.</em></p> <blockquote> <h2>v1.6.0</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>✨ feat(py_info): add system_exe, a narrowed system executable by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/python-discovery/pull/127">tox-dev/python-discovery#127</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/python-discovery/compare/1.5.3...1.6.0">https://github.com/tox-dev/python-discovery/compare/1.5.3...1.6.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/python-discovery/blob/main/docs/changelog.rst">python-discovery's changelog</a>.</em></p> <blockquote> <h1>Features - 1.6.0</h1> <ul> <li>:attr:<code>~python_discovery.PythonInfo.system_exe</code> returns the executable of the system Python an interpreter is based on, falling back to :attr:<code>~python_discovery.PythonInfo.executable</code> the way :meth:<code>~python_discovery.PythonInfo.resolve_to_system</code> does. :attr:<code>~python_discovery.PythonInfo.system_executable</code> is <code>None</code> until resolution runs, so every consumer had to narrow a value discovery has already settled - by :user:<code>gaborbernat</code>. (:issue:<code>127</code>)</li> </ul> <hr /> <p>v1.5.3 (2026-08-24)</p> <hr /> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/python-discovery/commit/ba1a07280dcb842a8bf49b26cd9edc5bd524d691"><code>ba1a072</code></a> release 1.6.0</li> <li><a href="https://github.com/tox-dev/python-discovery/commit/c9f4e8586bf94d3d094375e4037ab99f2f88e1bf"><code>c9f4e85</code></a> ✨ feat(py_info): add system_exe, a narrowed system executable (<a href="https://redirect.github.com/tox-dev/python-discovery/issues/127">#127</a>)</li> <li><a href="https://github.com/tox-dev/python-discovery/commit/0ef757b00a6f859529193eec31667f0ccc8b833b"><code>0ef757b</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/tox-dev/python-discovery/issues/126">#126</a>)</li> <li>See full diff in <a href="https://github.com/tox-dev/python-discovery/compare/1.5.3...1.6.0">compare view</a></li> </ul> </details> <br /> [](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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [cryptography](https://github.com/pyca/cryptography) from 50.0.0 to 50.0.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst">cryptography's changelog</a>.</em></p> <blockquote> <p>50.0.1 - 2026-08-25</p> <pre><code> * Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 4.0.2. <p>.. _v50-0-0:<br /> </code></pre></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pyca/cryptography/commit/ffde75a2b594822c740a2e4748b56c00548302bf"><code>ffde75a</code></a> bump for 50.0.1 + changelog (<a href="https://redirect.github.com/pyca/cryptography/issues/15520">#15520</a>)</li> <li>See full diff in <a href="https://github.com/pyca/cryptography/compare/50.0.0...50.0.1">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [virtualenv](https://github.com/pypa/virtualenv) from 21.7.5 to 21.7.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pypa/virtualenv/releases">virtualenv's releases</a>.</em></p> <blockquote> <h2>21.7.7</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>📄 docs: document the interpreter names in an environment by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/pypa/virtualenv/pull/3225">pypa/virtualenv#3225</a></li> <li>🎨 refactor(create): read the system exe without narrowing by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/pypa/virtualenv/pull/3224">pypa/virtualenv#3224</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pypa/virtualenv/compare/21.7.6...21.7.7">https://github.com/pypa/virtualenv/compare/21.7.6...21.7.7</a></p> <h2>21.7.6</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>🐛 fix(create): name Windows venv exes after the interpreter by <a href="https://github.com/darrenhuai"><code>@darrenhuai</code></a> in <a href="https://redirect.github.com/pypa/virtualenv/pull/3223">pypa/virtualenv#3223</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pypa/virtualenv/compare/21.7.5...21.7.6">https://github.com/pypa/virtualenv/compare/21.7.5...21.7.6</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/virtualenv/blob/main/docs/changelog.rst">virtualenv's changelog</a>.</em></p> <blockquote> <h1>Bugfixes - 21.7.7</h1> <ul> <li>Bump the <code>python-discovery</code> minimum to <code>>=1.6</code> for <code>PythonInfo.system_exe</code>, which reports the system interpreter without the nullable typing of <code>system_executable</code> - by :user:<code>gaborbernat</code>. (:issue:<code>3224</code>)</li> </ul> <h1>Improved Documentation - 21.7.7</h1> <ul> <li>Document the names the interpreter answers to inside a created environment. A new :doc:<code>reference/environment-layout</code> page lists them per platform, the tutorial and the usage guide point at it, and the explanation of creators covers why an environment carries several names and why Windows copies a redirector - by :user:<code>gaborbernat</code>. (:issue:<code>3225</code>)</li> </ul> <hr /> <p>v21.7.6 (2026-08-28)</p> <hr /> <h1>Bugfixes - 21.7.6</h1> <ul> <li>On Windows, <code>virtualenv</code> no longer copies the CPython 3.13+ <code>venvlauncher.exe</code> shim into <code>Scripts</code> under the shim's own name, and a host such as <code>python_d.exe</code> gets its alias back. The alias set took its names from the shim that stands in for the interpreter, so every environment gained a stray launcher copy and lost the interpreter's own file name - by :user:<code>darrenhuai</code>. (:issue:<code>3223</code>)</li> </ul> <hr /> <p>v21.7.5 (2026-08-25)</p> <hr /> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/virtualenv/commit/b65d93df5e727effffdd61a4e8be9f1a7f64b369"><code>b65d93d</code></a> release 21.7.7</li> <li><a href="https://github.com/pypa/virtualenv/commit/72776f2e7922aa0c442324b8b89b44d82d8e4445"><code>72776f2</code></a> 🎨 refactor(create): read the system exe without narrowing (<a href="https://redirect.github.com/pypa/virtualenv/issues/3224">#3224</a>)</li> <li><a href="https://github.com/pypa/virtualenv/commit/8fab8d6ac125afcd0c41b806064daf0521faaecd"><code>8fab8d6</code></a> 📄 docs: document the interpreter names in an environment (<a href="https://redirect.github.com/pypa/virtualenv/issues/3225">#3225</a>)</li> <li><a href="https://github.com/pypa/virtualenv/commit/267f4cda46d450138750448bef10cb7758834772"><code>267f4cd</code></a> release 21.7.6</li> <li><a href="https://github.com/pypa/virtualenv/commit/28c4cd14d60887567c72df6eb2254e0deba11ea0"><code>28c4cd1</code></a> 🐛 fix(create): name Windows venv exes after the interpreter (<a href="https://redirect.github.com/pypa/virtualenv/issues/3223">#3223</a>)</li> <li>See full diff in <a href="https://github.com/pypa/virtualenv/compare/21.7.5...21.7.7">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )