| commit | 82054683dd7ecd6db2304e8a26e6b1b6f2497da9 | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Sat Jun 15 00:02:35 2024 +0000 |
| committer | GitHub <noreply@github.com> | Sat Jun 15 00:02:35 2024 +0000 |
| tree | 14cc4620bc298f1a34ca1166c9a3e7535ed30bb5 | |
| parent | 7a437cc94ff722d8c088ab6140b0cd940d28c4d7 [diff] |
build(deps): bump typing-extensions from 4.9.0 to 4.12.2 in /docs/sphinx (#1965) Bumps [typing-extensions](https://github.com/python/typing_extensions) from 4.9.0 to 4.12.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/python/typing_extensions/releases">typing-extensions's releases</a>.</em></p> <blockquote> <h2>4.12.2</h2> <ul> <li>Fix regression in v4.12.0 where specialization of certain generics with an overridden <code>__eq__</code> method would raise errors. Patch by Jelle Zijlstra.</li> <li>Fix tests so they pass on 3.13.0b2</li> </ul> <h2>4.12.1</h2> <ul> <li>Preliminary changes for compatibility with the draft implementation of PEP 649 in Python 3.14. Patch by Jelle Zijlstra.</li> <li>Fix regression in v4.12.0 where nested <code>Annotated</code> types would cause <code>TypeError</code> to be raised if the nested <code>Annotated</code> type had unhashable metadata. Patch by Alex Waygood.</li> </ul> <h2>4.12.0</h2> <p>This release focuses on compatibility with the upcoming release of Python 3.13. Most changes are related to the implementation of type parameter defaults (PEP 696).</p> <p>Thanks to all of the people who contributed patches, especially Alex Waygood, who did most of the work adapting typing-extensions to the CPython PEP 696 implementation.</p> <p>There is a single change since 4.12.0rc1:</p> <ul> <li>Fix incorrect behaviour of <code>typing_extensions.ParamSpec</code> on Python 3.8 and 3.9 that meant that <code>isinstance(typing_extensions.ParamSpec("P"), typing.TypeVar)</code> would have a different result in some situations depending on whether or not a profiling function had been set using <code>sys.setprofile</code>. Patch by Alex Waygood.</li> </ul> <p>Changes included in 4.12.0rc1:</p> <ul> <li>Improve the implementation of type parameter defaults (PEP 696) <ul> <li>Backport the <code>typing.NoDefault</code> sentinel object from Python 3.13. TypeVars, ParamSpecs and TypeVarTuples without default values now have their <code>__default__</code> attribute set to this sentinel value.</li> <li>TypeVars, ParamSpecs and TypeVarTuples now have a <code>has_default()</code> method, matching <code>typing.TypeVar</code>, <code>typing.ParamSpec</code> and <code>typing.TypeVarTuple</code> on Python 3.13+.</li> <li>TypeVars, ParamSpecs and TypeVarTuples with <code>default=None</code> passed to their constructors now have their <code>__default__</code> attribute set to <code>None</code> at runtime rather than <code>types.NoneType</code>.</li> <li>Fix most tests for <code>TypeVar</code>, <code>ParamSpec</code> and <code>TypeVarTuple</code> on Python 3.13.0b1 and newer.</li> <li>Backport CPython PR <a href="https://redirect.github.com/python/cpython/pull/118774">#118774</a>, allowing type parameters without default values to follow those with default values in some type parameter lists. Patch by Alex Waygood, backporting a CPython PR by Jelle Zijlstra.</li> <li>It is now disallowed to use a <code>TypeVar</code> with a default value after a <code>TypeVarTuple</code> in a type parameter list. This matches the CPython implementation of PEP 696 on Python 3.13+.</li> <li>Fix bug in PEP-696 implementation where a default value for a <code>ParamSpec</code></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/python/typing_extensions/blob/main/CHANGELOG.md">typing-extensions's changelog</a>.</em></p> <blockquote> <h1>Release 4.12.2 (June 7, 2024)</h1> <ul> <li>Add <code>typing_extensions.get_annotations</code>, a backport of <code>inspect.get_annotations</code> that adds features specified by PEP 649. Patch by Jelle Zijlstra.</li> <li>Fix regression in v4.12.0 where specialization of certain generics with an overridden <code>__eq__</code> method would raise errors. Patch by Jelle Zijlstra.</li> <li>Fix tests so they pass on 3.13.0b2</li> </ul> <h1>Release 4.12.1 (June 1, 2024)</h1> <ul> <li>Preliminary changes for compatibility with the draft implementation of PEP 649 in Python 3.14. Patch by Jelle Zijlstra.</li> <li>Fix regression in v4.12.0 where nested <code>Annotated</code> types would cause <code>TypeError</code> to be raised if the nested <code>Annotated</code> type had unhashable metadata. Patch by Alex Waygood.</li> </ul> <h1>Release 4.12.0 (May 23, 2024)</h1> <p>This release is mostly the same as 4.12.0rc1 but fixes one more longstanding bug.</p> <ul> <li>Fix incorrect behaviour of <code>typing_extensions.ParamSpec</code> on Python 3.8 and 3.9 that meant that <code>isinstance(typing_extensions.ParamSpec("P"), typing.TypeVar)</code> would have a different result in some situations depending on whether or not a profiling function had been set using <code>sys.setprofile</code>. Patch by Alex Waygood.</li> </ul> <h1>Release 4.12.0rc1 (May 16, 2024)</h1> <p>This release focuses on compatibility with the upcoming release of Python 3.13. Most changes are related to the implementation of type parameter defaults (PEP 696).</p> <p>Thanks to all of the people who contributed patches, especially Alex Waygood, who did most of the work adapting typing-extensions to the CPython PEP 696 implementation.</p> <p>Full changelog:</p> <ul> <li>Improve the implementation of type parameter defaults (PEP 696) <ul> <li>Backport the <code>typing.NoDefault</code> sentinel object from Python 3.13. TypeVars, ParamSpecs and TypeVarTuples without default values now have their <code>__default__</code> attribute set to this sentinel value.</li> <li>TypeVars, ParamSpecs and TypeVarTuples now have a <code>has_default()</code> method, matching <code>typing.TypeVar</code>, <code>typing.ParamSpec</code> and <code>typing.TypeVarTuple</code> on Python 3.13+.</li> <li>TypeVars, ParamSpecs and TypeVarTuples with <code>default=None</code> passed to their constructors now have their <code>__default__</code> attribute set to <code>None</code></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/python/typing_extensions/commit/e1250ff869e7ee5ad05170d8a4b65469f13801c3"><code>e1250ff</code></a> Prepare release 4.12.2 (<a href="https://redirect.github.com/python/typing_extensions/issues/426">#426</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/53bcdded534494674f893112f71d3be344d65363"><code>53bcdde</code></a> Avoid error if origin has a buggy <strong>eq</strong> (<a href="https://redirect.github.com/python/typing_extensions/issues/422">#422</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/726963800030ab35ba5b975fc3a60486c26c5050"><code>7269638</code></a> Prepare release 4.12.1 (<a href="https://redirect.github.com/python/typing_extensions/issues/418">#418</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/8dfcf3c74a4f5d736a6d2ce8d82c3e85cd0c5b18"><code>8dfcf3c</code></a> Fix <code>TypeError</code> on nested <code>Annotated</code> types where the inner type has unhashab...</li> <li><a href="https://github.com/python/typing_extensions/commit/d76f5911b7d44aa1ff26de22e76047ca6c53f840"><code>d76f591</code></a> Switch from flake8 to ruff (<a href="https://redirect.github.com/python/typing_extensions/issues/414">#414</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/920d60d09e929e23657a4459dd446fb428715981"><code>920d60d</code></a> Support my PEP 649 branch (<a href="https://redirect.github.com/python/typing_extensions/issues/412">#412</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/e792bce5508dad9f5f00066ad615d231cc1d64c1"><code>e792bce</code></a> Ignore fewer flake8 rules when linting tests (<a href="https://redirect.github.com/python/typing_extensions/issues/413">#413</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/f90a8dc40b60bf43510b8611a07d8cc570544ffe"><code>f90a8dc</code></a> Prepare release 4.12.0 (<a href="https://redirect.github.com/python/typing_extensions/issues/408">#408</a>)</li> <li><a href="https://github.com/python/typing_extensions/commit/118e1a604a857d54cb70a2a1f930b425676d6cb4"><code>118e1a6</code></a> Make sure <code>isinstance(typing_extensions.ParamSpec("P"), typing.TypeVar)</code> is u...</li> <li><a href="https://github.com/python/typing_extensions/commit/910141ab8295b422851f83ffc46c9eb04bbca719"><code>910141a</code></a> Add security documentation (<a href="https://redirect.github.com/python/typing_extensions/issues/403">#403</a>)</li> <li>Additional commits viewable in <a href="https://github.com/python/typing_extensions/compare/4.9.0...4.12.2">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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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>
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
Currently, the core rules build into the Bazel binary, and the symbols in this repository are simple aliases. However, we are migrating the rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. SeeMigrating from the Bundled Rules below.
The core rules are stable. Their implementation in Bazel is subject to Bazel's backward compatibility policy. Once migrated to rules_python, they may evolve at a different rate, but this repository will still follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.