[pull] master from aio-libs:master #123
Merged
Conversation
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
Bumps [pygments](https://github.com/pygments/pygments) from 2.18.0 to 2.19.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pygments/pygments/releases">pygments's releases</a>.</em></p> <blockquote> <h2>2.19.0</h2> <ul> <li> <p>New lexers:</p> <ul> <li>CodeQL (<a href="https://redirect.github.com/pygments/pygments/issues/2819">#2819</a>)</li> <li>Debian Sources (<a href="https://redirect.github.com/pygments/pygments/issues/2788">#2788</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2747">#2747</a>)</li> <li>Gleam (<a href="https://redirect.github.com/pygments/pygments/issues/2662">#2662</a>)</li> <li>GoogleSQL (<a href="https://redirect.github.com/pygments/pygments/issues/2820">#2820</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2814">#2814</a>)</li> <li>JSON5 (<a href="https://redirect.github.com/pygments/pygments/issues/2734">#2734</a>, <a href="https://redirect.github.com/pygments/pygments/issues/1880">#1880</a>)</li> <li>Maple (<a href="https://redirect.github.com/pygments/pygments/issues/2763">#2763</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2548">#2548</a>)</li> <li>NumbaIR (<a href="https://redirect.github.com/pygments/pygments/issues/2433">#2433</a>)</li> <li>PDDL (<a href="https://redirect.github.com/pygments/pygments/issues/2799">#2799</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2616">#2616</a>)</li> <li>Rego (<a href="https://redirect.github.com/pygments/pygments/issues/2794">#2794</a>)</li> <li>TableGen (<a href="https://redirect.github.com/pygments/pygments/issues/2751">#2751</a>)</li> <li>Vue.js (<a href="https://redirect.github.com/pygments/pygments/issues/2832">#2832</a>)</li> </ul> </li> <li> <p>Updated lexers:</p> <ul> <li>BQN: Various improvements (<a href="https://redirect.github.com/pygments/pygments/issues/2789">#2789</a>)</li> <li>C#: Fix number highlighting (<a href="https://redirect.github.com/pygments/pygments/issues/986">#986</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2727">#2727</a>), add <code>file</code> keyword (<a href="https://redirect.github.com/pygments/pygments/issues/2726">#2726</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2805">#2805</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2806">#2806</a>), add various other keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2745">#2745</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2770">#2770</a>)</li> <li>CSS: Add <code>revert</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2766">#2766</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2775">#2775</a>)</li> <li>Debian control: Add <code>Change-By</code> field (<a href="https://redirect.github.com/pygments/pygments/issues/2757">#2757</a>)</li> <li>Elip: Improve punctuation handling (<a href="https://redirect.github.com/pygments/pygments/issues/2651">#2651</a>)</li> <li>Igor: Add <code>int</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2801">#2801</a>)</li> <li>Ini: Fix quoted strings with embedded comment characters (<a href="https://redirect.github.com/pygments/pygments/issues/2767">#2767</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2720">#2720</a>)</li> <li>Java: Support functions returning types containing a question mark (<a href="https://redirect.github.com/pygments/pygments/issues/2737">#2737</a>)</li> <li>JavaScript: Support private identiiers (<a href="https://redirect.github.com/pygments/pygments/issues/2729">#2729</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2671">#2671</a>)</li> <li>LLVM: Add <code>splat</code>, improve floating-point number parsing (<a href="https://redirect.github.com/pygments/pygments/issues/2755">#2755</a>)</li> <li>Lua: Improve variable detection, add built-in functions (<a href="https://redirect.github.com/pygments/pygments/issues/2829">#2829</a>)</li> <li>Macaulay2: Update to 1.24.11 (<a href="https://redirect.github.com/pygments/pygments/issues/2800">#2800</a>)</li> <li>PostgreSQL: Add more <code>EXPLAIN</code> keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2785">#2785</a>), handle <code>/</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2774">#2774</a>)</li> <li>S-Lexer: Fix keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2082">#2082</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2750">#2750</a>)</li> <li>TransactSQL: Fix single-line comments (<a href="https://redirect.github.com/pygments/pygments/issues/2717">#2717</a>)</li> <li>Turtle: Fix triple quoted strings (<a href="https://redirect.github.com/pygments/pygments/issues/2744">#2744</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2758">#2758</a>)</li> <li>Typst: Various improvements (<a href="https://redirect.github.com/pygments/pygments/issues/2724">#2724</a>)</li> <li>Various: Add <code>^</code> as an operator to Matlab, Octave and Scilab (<a href="https://redirect.github.com/pygments/pygments/issues/2798">#2798</a>)</li> <li>Vyper: Add <code>staticcall</code> and <code>extcall</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2719">#2719</a>)</li> </ul> </li> </ul> <ul> <li>Mark file extensions for <code>HTML/XML+Evoque</code> as aliases (<a href="https://redirect.github.com/pygments/pygments/issues/2743">#2743</a>)</li> <li>Add a color for <code>Operator.Word</code> to the <code>rrt</code> style (<a href="https://redirect.github.com/pygments/pygments/issues/2709">#2709</a>)</li> <li>Fix broken link in the documentation (<a href="https://redirect.github.com/pygments/pygments/issues/2803">#2803</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2804">#2804</a>)</li> <li>Drop executable bit where not needed (<a href="https://redirect.github.com/pygments/pygments/issues/2781">#2781</a>)</li> <li>Reduce Mojo priority relative to Python in ``analyze_text´` (<a href="https://redirect.github.com/pygments/pygments/issues/2771">#2771</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2772">#2772</a>)</li> <li>Fix documentation builds (<a href="https://redirect.github.com/pygments/pygments/issues/2712">#2712</a>)</li> <li>Match example file names to the lexer's name (<a href="https://redirect.github.com/pygments/pygments/issues/2713">#2713</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2715">#2715</a>)</li> <li>Ensure lexer metadata is present (<a href="https://redirect.github.com/pygments/pygments/issues/2714">#2714</a>)</li> <li>Search more directories on macOS for fonts (<a href="https://redirect.github.com/pygments/pygments/issues/2809">#2809</a>)</li> <li>Improve test robustness (<a href="https://redirect.github.com/pygments/pygments/issues/2812">#2812</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pygments/pygments/blob/master/CHANGES">pygments's changelog</a>.</em></p> <blockquote> <h2>Version 2.19.0</h2> <p>(released January 5th, 2025)</p> <ul> <li> <p>New lexers:</p> <ul> <li>CodeQL (<a href="https://redirect.github.com/pygments/pygments/issues/2819">#2819</a>)</li> <li>Debian Sources (<a href="https://redirect.github.com/pygments/pygments/issues/2788">#2788</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2747">#2747</a>)</li> <li>Gleam (<a href="https://redirect.github.com/pygments/pygments/issues/2662">#2662</a>)</li> <li>GoogleSQL (<a href="https://redirect.github.com/pygments/pygments/issues/2820">#2820</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2814">#2814</a>)</li> <li>JSON5 (<a href="https://redirect.github.com/pygments/pygments/issues/2734">#2734</a>, <a href="https://redirect.github.com/pygments/pygments/issues/1880">#1880</a>)</li> <li>Maple (<a href="https://redirect.github.com/pygments/pygments/issues/2763">#2763</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2548">#2548</a>)</li> <li>NumbaIR (<a href="https://redirect.github.com/pygments/pygments/issues/2433">#2433</a>)</li> <li>PDDL (<a href="https://redirect.github.com/pygments/pygments/issues/2799">#2799</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2616">#2616</a>)</li> <li>Rego (<a href="https://redirect.github.com/pygments/pygments/issues/2794">#2794</a>)</li> <li>TableGen (<a href="https://redirect.github.com/pygments/pygments/issues/2751">#2751</a>)</li> <li>Vue.js (<a href="https://redirect.github.com/pygments/pygments/issues/2832">#2832</a>)</li> </ul> </li> <li> <p>Updated lexers:</p> <ul> <li>BQN: Various improvements (<a href="https://redirect.github.com/pygments/pygments/issues/2789">#2789</a>)</li> <li>C#: Fix number highlighting (<a href="https://redirect.github.com/pygments/pygments/issues/986">#986</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2727">#2727</a>), add <code>file</code> keyword (<a href="https://redirect.github.com/pygments/pygments/issues/2726">#2726</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2805">#2805</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2806">#2806</a>), add various other keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2745">#2745</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2770">#2770</a>)</li> <li>CSS: Add <code>revert</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2766">#2766</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2775">#2775</a>)</li> <li>Debian control: Add <code>Change-By</code> field (<a href="https://redirect.github.com/pygments/pygments/issues/2757">#2757</a>)</li> <li>Elip: Improve punctuation handling (<a href="https://redirect.github.com/pygments/pygments/issues/2651">#2651</a>)</li> <li>Igor: Add <code>int</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2801">#2801</a>)</li> <li>Ini: Fix quoted strings with embedded comment characters (<a href="https://redirect.github.com/pygments/pygments/issues/2767">#2767</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2720">#2720</a>)</li> <li>Java: Support functions returning types containing a question mark (<a href="https://redirect.github.com/pygments/pygments/issues/2737">#2737</a>)</li> <li>JavaScript: Support private identiiers (<a href="https://redirect.github.com/pygments/pygments/issues/2729">#2729</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2671">#2671</a>)</li> <li>LLVM: Add <code>splat</code>, improve floating-point number parsing (<a href="https://redirect.github.com/pygments/pygments/issues/2755">#2755</a>)</li> <li>Lua: Improve variable detection, add built-in functions (<a href="https://redirect.github.com/pygments/pygments/issues/2829">#2829</a>)</li> <li>Macaulay2: Update to 1.24.11 (<a href="https://redirect.github.com/pygments/pygments/issues/2800">#2800</a>)</li> <li>PostgreSQL: Add more <code>EXPLAIN</code> keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2785">#2785</a>), handle <code>/</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2774">#2774</a>)</li> <li>S-Lexer: Fix keywords (<a href="https://redirect.github.com/pygments/pygments/issues/2082">#2082</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2750">#2750</a>)</li> <li>TransactSQL: Fix single-line comments (<a href="https://redirect.github.com/pygments/pygments/issues/2717">#2717</a>)</li> <li>Turtle: Fix triple quoted strings (<a href="https://redirect.github.com/pygments/pygments/issues/2744">#2744</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2758">#2758</a>)</li> <li>Typst: Various improvements (<a href="https://redirect.github.com/pygments/pygments/issues/2724">#2724</a>)</li> <li>Various: Add <code>^</code> as an operator to Matlab, Octave and Scilab (<a href="https://redirect.github.com/pygments/pygments/issues/2798">#2798</a>)</li> <li>Vyper: Add <code>staticcall</code> and <code>extcall</code> (<a href="https://redirect.github.com/pygments/pygments/issues/2719">#2719</a>)</li> </ul> </li> </ul> <ul> <li>Mark file extensions for <code>HTML/XML+Evoque</code> as aliases (<a href="https://redirect.github.com/pygments/pygments/issues/2743">#2743</a>)</li> <li>Add a color for <code>Operator.Word</code> to the <code>rrt</code> style (<a href="https://redirect.github.com/pygments/pygments/issues/2709">#2709</a>)</li> <li>Fix broken link in the documentation (<a href="https://redirect.github.com/pygments/pygments/issues/2803">#2803</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2804">#2804</a>)</li> <li>Drop executable bit where not needed (<a href="https://redirect.github.com/pygments/pygments/issues/2781">#2781</a>)</li> <li>Reduce Mojo priority relative to Python in ``analyze_text´` (<a href="https://redirect.github.com/pygments/pygments/issues/2771">#2771</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2772">#2772</a>)</li> <li>Fix documentation builds (<a href="https://redirect.github.com/pygments/pygments/issues/2712">#2712</a>)</li> <li>Match example file names to the lexer's name (<a href="https://redirect.github.com/pygments/pygments/issues/2713">#2713</a>, <a href="https://redirect.github.com/pygments/pygments/issues/2715">#2715</a>)</li> <li>Ensure lexer metadata is present (<a href="https://redirect.github.com/pygments/pygments/issues/2714">#2714</a>)</li> <li>Search more directories on macOS for fonts (<a href="https://redirect.github.com/pygments/pygments/issues/2809">#2809</a>)</li> <li>Improve test robustness (<a href="https://redirect.github.com/pygments/pygments/issues/2812">#2812</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pygments/pygments/commit/62dff316900a548aabf741d662b79edc39ed78b5"><code>62dff31</code></a> Prepare 2.19 release.</li> <li><a href="https://github.com/pygments/pygments/commit/0ee47fb292be8142f359c5ae94472a508a69ba6d"><code>0ee47fb</code></a> It's 2025.</li> <li><a href="https://github.com/pygments/pygments/commit/3f79c5d8d0c686e58a199aff479e42b3caeb7370"><code>3f79c5d</code></a> Check fixes.</li> <li><a href="https://github.com/pygments/pygments/commit/ed139881e3f4e39cd4db076c87e4b118d91ac705"><code>ed13988</code></a> Small fixes for Maple lexer.</li> <li><a href="https://github.com/pygments/pygments/commit/a522163c58feb0d15d44dddc123dcdd495bea572"><code>a522163</code></a> Merge pull request <a href="https://redirect.github.com/pygments/pygments/issues/2763">#2763</a> from Randl/master</li> <li><a href="https://github.com/pygments/pygments/commit/69216f7914b2fb5648e8ba9aabb953f22efb18d6"><code>69216f7</code></a> Small fixes for Numba IR.</li> <li><a href="https://github.com/pygments/pygments/commit/08b8a96e69490497959b91ade089f1fa80768b99"><code>08b8a96</code></a> Merge pull request <a href="https://redirect.github.com/pygments/pygments/issues/2433">#2433</a> from Matt711/numbair</li> <li><a href="https://github.com/pygments/pygments/commit/9ac75ea5a04cc6405c5055e87a419b2d8827af87"><code>9ac75ea</code></a> Small fixups for CodeQL.</li> <li><a href="https://github.com/pygments/pygments/commit/ef4f5e9a343a7d6e095d604e9843a29ac9f1ea3a"><code>ef4f5e9</code></a> Merge pull request <a href="https://redirect.github.com/pygments/pygments/issues/2819">#2819</a> from DarkaMaul/dm/add-codeql-lexer</li> <li><a href="https://github.com/pygments/pygments/commit/2dc2c3fc292f77dc9b71c4d59d489a82f4d43473"><code>2dc2c3f</code></a> Merge branch 'master' into dm/add-codeql-lexer</li> <li>Additional commits viewable in <a href="https://github.com/pygments/pygments/compare/2.18.0...2.19.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 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>
Bumps [identify](https://github.com/pre-commit/identify) from 2.6.4 to 2.6.5. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pre-commit/identify/commit/1eadcb782d64c204597ec6b2142982a89ebda7ed"><code>1eadcb7</code></a> v2.6.5</li> <li><a href="https://github.com/pre-commit/identify/commit/2bb89b8d7e1e4971709db4261403c1c9605629de"><code>2bb89b8</code></a> Merge pull request <a href="https://redirect.github.com/pre-commit/identify/issues/498">#498</a> from MatejKafka/main</li> <li><a href="https://github.com/pre-commit/identify/commit/3fa1e74cedb42eeeaee6088578c78a412891f269"><code>3fa1e74</code></a> feat: identify .psm1 and .psd1 files as powershell</li> <li>See full diff in <a href="https://github.com/pre-commit/identify/compare/v2.6.4...v2.6.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 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>
Bumps [setuptools](https://github.com/pypa/setuptools) from 75.6.0 to 75.7.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/setuptools/blob/main/NEWS.rst">setuptools's changelog</a>.</em></p> <blockquote> <h1>v75.7.0</h1> <h2>Features</h2> <ul> <li><code>pypa/distutils#310</code><a href="https://redirect.github.com/pypa/setuptools/issues/4478">#4478</a>)</li> <li>Synced with pypa/distutils@ff11eed0c including bugfix for duplicate CFLAGS and adaption to support Python 3.13 is_abs in the C compiler (<a href="https://redirect.github.com/pypa/setuptools/issues/4669">#4669</a>). (<a href="https://redirect.github.com/pypa/setuptools/issues/4790">#4790</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/setuptools/commit/4e82e8b75c8bd8cba1232a107dc171b4fd2c588c"><code>4e82e8b</code></a> Bump version: 75.6.0 → 75.7.0</li> <li><a href="https://github.com/pypa/setuptools/commit/50b15dbedc3a5665717b9204cd85291152f5b314"><code>50b15db</code></a> Merge pull request <a href="https://redirect.github.com/pypa/setuptools/issues/4787">#4787</a> from Avasam/simplify-typed-assignements</li> <li><a href="https://github.com/pypa/setuptools/commit/86d8c992fc201fae91d135019e5abada183548e2"><code>86d8c99</code></a> Merge pull request <a href="https://redirect.github.com/pypa/setuptools/issues/4790">#4790</a> from pypa/feature/distutils-ff11eed0c</li> <li><a href="https://github.com/pypa/setuptools/commit/c384f184d20e8232a1ce73f88d151b9808b66949"><code>c384f18</code></a> Py_GIL_Disabled was handled previously.</li> <li><a href="https://github.com/pypa/setuptools/commit/fbe834af40de70c181cd2ff5395f8e3488177874"><code>fbe834a</code></a> Merge branch 'main' into feature/distutils-ff11eed0c</li> <li><a href="https://github.com/pypa/setuptools/commit/5ed9d93e77aa3e2c70d8cea1bfeb15549932169f"><code>5ed9d93</code></a> Add news fragment.</li> <li><a href="https://github.com/pypa/setuptools/commit/e94ce0d2aa2d38b67e5c7ee84ca53fde9d4b5b28"><code>e94ce0d</code></a> Merge with pypa/distutils.</li> <li><a href="https://github.com/pypa/setuptools/commit/ff11eed0c36b35bd68615a8ebf36763b7c8a6f28"><code>ff11eed</code></a> Merge pull request <a href="https://redirect.github.com/pypa/distutils/issues/325">pypa/distutils#325</a> from thesamesam/cflags</li> <li><a href="https://github.com/pypa/setuptools/commit/ebfebc096000e16f9d640660047eaec891a98529"><code>ebfebc0</code></a> Merge pull request <a href="https://redirect.github.com/pypa/distutils/issues/302">pypa/distutils#302</a> from adang1345/fix-python313-abs</li> <li><a href="https://github.com/pypa/setuptools/commit/36ce8b329524088cfa53b9a4bffcce3a8d233539"><code>36ce8b3</code></a> Refactor for simplicity.</li> <li>Additional commits viewable in <a href="https://github.com/pypa/setuptools/compare/v75.6.0...v75.7.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 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>
pull bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
…load-artifact v4 and download-artifact v4 (aio-libs#10289) **This is a backport of PR aio-libs#10281 as merged into master (d54b3e2).** <!-- Thank you for your contribution! --> ## What do these changes do? This updates the ci/cd workflow to use the upload-artifact v4 and download-artifact v4 github actions. The currently used upload-artifact and download-artifact will no longer work at the end of next month. The changes are needed since v4 no longer has mutable artifacts, which was used to collect wheels from different architectures. Fix aio-libs#8588, Fix aio-libs#8589, Fix aio-libs#9009, Fix aio-libs#10189, Fix aio-libs#10191 ## Are there changes in behavior for the user? No, the ci/cd workflow has been tested although without publishing. ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [x] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. Co-authored-by: Simon Lamon <32477463+silamon@users.noreply.github.com>
pull bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
…load-artifact v4 and download-artifact v4 (aio-libs#10288) **This is a backport of PR aio-libs#10281 as merged into master (d54b3e2).** <!-- Thank you for your contribution! --> ## What do these changes do? This updates the ci/cd workflow to use the upload-artifact v4 and download-artifact v4 github actions. The currently used upload-artifact and download-artifact will no longer work at the end of next month. The changes are needed since v4 no longer has mutable artifacts, which was used to collect wheels from different architectures. Fix aio-libs#8588, Fix aio-libs#8589, Fix aio-libs#9009, Fix aio-libs#10189, Fix aio-libs#10191 ## Are there changes in behavior for the user? No, the ci/cd workflow has been tested although without publishing. ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [x] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. Co-authored-by: Simon Lamon <32477463+silamon@users.noreply.github.com>
pull bot
pushed a commit
that referenced
this pull request
Mar 16, 2025
Instead of TCPConnector taking a list of sockopts to be applied sockets created, take a socket_factory callback that allows the caller to implement socket creation entirely. Fixes aio-libs#10520 <!-- Thank you for your contribution! --> ## What do these changes do? Replace `tcp_sockopts` parameter with a `socket_factory` parameter that is a callback allowing the caller to own socket creation. If passed, all sockets created by `TCPConnector` are expected to come from the `socket_factory` callback. <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? The only users to experience a change in behavior are those who are using the un-released `tcp_sockopts` argument to `TCPConnector`. However, using unreleased code comes with caveat emptor, and is why I felt entitled to remove the option entirely without warning. <!-- Outline any notable behaviour for the end users. --> ## Is it a substantial burden for the maintainers to support this? The burden will be minimal and would only arise if `aiohappyeyeballs` changes their interface. <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [x] Unit tests for the changes exist - [x] Documentation reflects the changes - [x] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [x] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. --------- Co-authored-by: J. Nick Koston <nick@koston.org>
pull bot
pushed a commit
that referenced
this pull request
Mar 17, 2025
…ent-type (aio-libs#10557) **This is a backport of PR aio-libs#10552 as merged into master (44e669b).** <!-- Thank you for your contribution! --> ## What do these changes do? When profiling some frequent POST requests, I found the bulk of the time was spent parsing the content-type string. Use the same strategy as we do for `parse_mimetype` to cache the parsing. ## Are there changes in behavior for the user? performance improvement ## Is it a substantial burden for the maintainers to support this? no ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. <img width="570" alt="Screenshot 2025-03-15 at 11 25 10 AM" src="https://github.com/user-attachments/assets/cabaaa7c-3a39-4f90-b450-a6a0559d22d6" /> Co-authored-by: J. Nick Koston <nick@koston.org>
pull bot
pushed a commit
that referenced
this pull request
Mar 17, 2025
…ent-type (aio-libs#10558) **This is a backport of PR aio-libs#10552 as merged into master (44e669b).** <!-- Thank you for your contribution! --> ## What do these changes do? When profiling some frequent POST requests, I found the bulk of the time was spent parsing the content-type string. Use the same strategy as we do for `parse_mimetype` to cache the parsing. ## Are there changes in behavior for the user? performance improvement ## Is it a substantial burden for the maintainers to support this? no ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. <img width="570" alt="Screenshot 2025-03-15 at 11 25 10 AM" src="https://github.com/user-attachments/assets/cabaaa7c-3a39-4f90-b450-a6a0559d22d6" /> Co-authored-by: J. Nick Koston <nick@koston.org>
pull bot
pushed a commit
that referenced
this pull request
Mar 17, 2025
… socket_factory (aio-libs#10574) replaces and closes aio-libs#10565 Instead of TCPConnector taking a list of sockopts to be applied sockets created, take a socket_factory callback that allows the caller to implement socket creation entirely. Fixes aio-libs#10520 <!-- Thank you for your contribution! --> Replace `tcp_sockopts` parameter with a `socket_factory` parameter that is a callback allowing the caller to own socket creation. If passed, all sockets created by `TCPConnector` are expected to come from the `socket_factory` callback. <!-- Please give a short brief about these changes. --> The only users to experience a change in behavior are those who are using the un-released `tcp_sockopts` argument to `TCPConnector`. However, using unreleased code comes with caveat emptor, and is why I felt entitled to remove the option entirely without warning. <!-- Outline any notable behaviour for the end users. --> The burden will be minimal and would only arise if `aiohappyeyeballs` changes their interface. <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> - [x] I think the code is well written - [x] Unit tests for the changes exist - [x] Documentation reflects the changes - [x] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [x] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. --------- Co-authored-by: J. Nick Koston <nick@koston.org> (cherry picked from commit 3b9bb1c) <!-- Thank you for your contribution! --> ## What do these changes do? <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? <!-- Outline any notable behaviour for the end users. --> ## Is it a substantial burden for the maintainers to support this? <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> ## Related issue number <!-- Are there any issues opened that will be resolved by merging this change? --> <!-- Remember to prefix with 'Fixes' if it should close the issue (e.g. 'Fixes #123'). --> ## Checklist - [ ] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. Co-authored-by: Tim Menninger <tmenninger22@gmail.com>
pull bot
pushed a commit
that referenced
this pull request
May 12, 2025
Bumps [exceptiongroup](https://github.com/agronholm/exceptiongroup) from 1.2.2 to 1.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/releases">exceptiongroup's releases</a>.</em></p> <blockquote> <h2>1.3.0</h2> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/143">#143</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/blob/main/CHANGES.rst">exceptiongroup's changelog</a>.</em></p> <blockquote> <h1>Version history</h1> <p>This library adheres to <code>Semantic Versioning 2.0 <http://semver.org/></code>_.</p> <p><strong>1.3.0</strong></p> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<code>[#143](agronholm/exceptiongroup#143) <https://github.com/agronholm/exceptiongroup/issues/143></code>_)</li> </ul> <p><strong>1.2.2</strong></p> <ul> <li>Removed an <code>assert</code> in <code>exceptiongroup._formatting</code> that caused compatibility issues with Sentry (<code>[#123](agronholm/exceptiongroup#123) <https://github.com/agronholm/exceptiongroup/issues/123></code>_)</li> </ul> <p><strong>1.2.1</strong></p> <ul> <li>Updated the copying of <code>__notes__</code> to match CPython behavior (PR by CF Bolz-Tereick)</li> <li>Corrected the type annotation of the exception handler callback to accept a <code>BaseExceptionGroup</code> instead of <code>BaseException</code></li> <li>Fixed type errors on Python < 3.10 and the type annotation of <code>suppress()</code> (PR by John Litborn)</li> </ul> <p><strong>1.2.0</strong></p> <ul> <li>Added special monkeypatching if <code>Apport <https://github.com/canonical/apport></code>_ has overridden <code>sys.excepthook</code> so it will format exception groups correctly (PR by John Litborn)</li> <li>Added a backport of <code>contextlib.suppress()</code> from Python 3.12.1 which also handles suppressing exceptions inside exception groups</li> <li>Fixed bare <code>raise</code> in a handler reraising the original naked exception rather than an exception group which is what is raised when you do a <code>raise</code> in an <code>except*</code> handler</li> </ul> <p><strong>1.1.3</strong></p> <ul> <li><code>catch()</code> now raises a <code>TypeError</code> if passed an async exception handler instead of just giving a <code>RuntimeWarning</code> about the coroutine never being awaited. (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/66">#66</a>, PR by John Litborn)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/agronholm/exceptiongroup/commit/77fba8a871408ff2c48f536e5e73b1918239ba5f"><code>77fba8a</code></a> Added the release version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/5e153aa379ac53af79cc7f5e287f77929cb4d0dc"><code>5e153aa</code></a> Revert "Migrated test dependencies to dependency groups"</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/5000bfea208ad59e3a20e2fb91a513ad559711b1"><code>5000bfe</code></a> Migrated tox configuration to native TOML</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/427220d67a52585e98575103b090b5fdaf87a899"><code>427220d</code></a> Updated pytest options</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/4ca264fa3605d52067c20b351a0d3b947fa1f363"><code>4ca264f</code></a> Migrated test dependencies to dependency groups</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/163c3a8cb27f8a5325258b5a83e7cf8fc002c3b7"><code>163c3a8</code></a> Marked test_exceptions_mutate_original_sequence as xfail on pypy3.11</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/a1765740db2d55d1eb91d67a8fbbb355caf7881b"><code>a176574</code></a> Always create the exceptions tuple at init and return it from the exceptions ...</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/550b79621cc35892413fa91903a1d6c7951d0449"><code>550b796</code></a> Added BaseExceptionGroup.<strong>init</strong>, following CPython (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/142">#142</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/2a84dfd5599bca0c653143f0f4252d38afac9867"><code>2a84dfd</code></a> Added typevar defaults to (Base)ExceptionGroup (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/147">#147</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/fb9133b495fc82bc2907e8cfbdff6c6dc3087e2f"><code>fb9133b</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/145">#145</a>)</li> <li>Additional commits viewable in <a href="https://github.com/agronholm/exceptiongroup/compare/1.2.2...1.3.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 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>
pull bot
pushed a commit
that referenced
this pull request
May 24, 2025
Bumps [exceptiongroup](https://github.com/agronholm/exceptiongroup) from 1.2.2 to 1.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/releases">exceptiongroup's releases</a>.</em></p> <blockquote> <h2>1.3.0</h2> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/143">#143</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/blob/main/CHANGES.rst">exceptiongroup's changelog</a>.</em></p> <blockquote> <h1>Version history</h1> <p>This library adheres to <code>Semantic Versioning 2.0 <http://semver.org/></code>_.</p> <p><strong>1.3.0</strong></p> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<code>[#143](agronholm/exceptiongroup#143) <https://github.com/agronholm/exceptiongroup/issues/143></code>_)</li> </ul> <p><strong>1.2.2</strong></p> <ul> <li>Removed an <code>assert</code> in <code>exceptiongroup._formatting</code> that caused compatibility issues with Sentry (<code>[#123](agronholm/exceptiongroup#123) <https://github.com/agronholm/exceptiongroup/issues/123></code>_)</li> </ul> <p><strong>1.2.1</strong></p> <ul> <li>Updated the copying of <code>__notes__</code> to match CPython behavior (PR by CF Bolz-Tereick)</li> <li>Corrected the type annotation of the exception handler callback to accept a <code>BaseExceptionGroup</code> instead of <code>BaseException</code></li> <li>Fixed type errors on Python < 3.10 and the type annotation of <code>suppress()</code> (PR by John Litborn)</li> </ul> <p><strong>1.2.0</strong></p> <ul> <li>Added special monkeypatching if <code>Apport <https://github.com/canonical/apport></code>_ has overridden <code>sys.excepthook</code> so it will format exception groups correctly (PR by John Litborn)</li> <li>Added a backport of <code>contextlib.suppress()</code> from Python 3.12.1 which also handles suppressing exceptions inside exception groups</li> <li>Fixed bare <code>raise</code> in a handler reraising the original naked exception rather than an exception group which is what is raised when you do a <code>raise</code> in an <code>except*</code> handler</li> </ul> <p><strong>1.1.3</strong></p> <ul> <li><code>catch()</code> now raises a <code>TypeError</code> if passed an async exception handler instead of just giving a <code>RuntimeWarning</code> about the coroutine never being awaited. (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/66">#66</a>, PR by John Litborn)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/agronholm/exceptiongroup/commit/77fba8a871408ff2c48f536e5e73b1918239ba5f"><code>77fba8a</code></a> Added the release version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/5e153aa379ac53af79cc7f5e287f77929cb4d0dc"><code>5e153aa</code></a> Revert "Migrated test dependencies to dependency groups"</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/5000bfea208ad59e3a20e2fb91a513ad559711b1"><code>5000bfe</code></a> Migrated tox configuration to native TOML</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/427220d67a52585e98575103b090b5fdaf87a899"><code>427220d</code></a> Updated pytest options</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/4ca264fa3605d52067c20b351a0d3b947fa1f363"><code>4ca264f</code></a> Migrated test dependencies to dependency groups</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/163c3a8cb27f8a5325258b5a83e7cf8fc002c3b7"><code>163c3a8</code></a> Marked test_exceptions_mutate_original_sequence as xfail on pypy3.11</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/a1765740db2d55d1eb91d67a8fbbb355caf7881b"><code>a176574</code></a> Always create the exceptions tuple at init and return it from the exceptions ...</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/550b79621cc35892413fa91903a1d6c7951d0449"><code>550b796</code></a> Added BaseExceptionGroup.<strong>init</strong>, following CPython (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/142">#142</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/2a84dfd5599bca0c653143f0f4252d38afac9867"><code>2a84dfd</code></a> Added typevar defaults to (Base)ExceptionGroup (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/147">#147</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/fb9133b495fc82bc2907e8cfbdff6c6dc3087e2f"><code>fb9133b</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/145">#145</a>)</li> <li>Additional commits viewable in <a href="https://github.com/agronholm/exceptiongroup/compare/1.2.2...1.3.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 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>
pull bot
pushed a commit
that referenced
this pull request
Jul 10, 2025
Bumps [aiosignal](https://github.com/aio-libs/aiosignal) from 1.3.2 to 1.4.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aio-libs/aiosignal/releases">aiosignal's releases</a>.</em></p> <blockquote> <h2>1.4.0</h2> <h2>Features</h2> <ul> <li> <p>Added decorator functionality to <code>Signal</code> as a convenient way to add a callback -- by <code>@Vizonex</code>. <code>[aio-libs#699](aio-libs/aiosignal#699) <https://github.com/aio-libs/aiosignal/pulls/699></code>_</p> </li> <li> <p>Improved type safety by allowing callback parameters to be type checked (typing-extensions is now required for Python <3.13). Parameters for a <code>Signal</code> callback should now be defined like <code>Signal[int, str]</code> -- by <a href="https://github.com/Vizonex"><code>@Vizonex</code></a> and <a href="https://github.com/Dreamsorcerer"><code>@Dreamsorcerer</code></a>. <code>[aio-libs#699](aio-libs/aiosignal#699) <https://github.com/aio-libs/aiosignal/pulls/699></code><em>, <code>[aio-libs#710](aio-libs/aiosignal#710) <https://github.com/aio-libs/aiosignal/pulls/710></code></em></p> </li> </ul> <h2>Misc</h2> <ul> <li>Removed the sphinxcontrib-asyncio documentation dependency. <code>[aio-libs#528](aio-libs/aiosignal#528) <https://github.com/aio-libs/aiosignal/pull/528></code>_</li> </ul> <hr /> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aio-libs/aiosignal/blob/master/CHANGES.rst">aiosignal's changelog</a>.</em></p> <blockquote> <h1>1.4.0 (2025-07-03)</h1> <h2>Features</h2> <ul> <li> <p>Added decorator functionality to <code>Signal</code> as a convenient way to add a callback -- by <code>@Vizonex</code>. <code>[aio-libs#699](aio-libs/aiosignal#699) <https://github.com/aio-libs/aiosignal/pulls/699></code>_</p> </li> <li> <p>Improved type safety by allowing callback parameters to be type checked (typing-extensions is now required for Python <3.13). Parameters for a <code>Signal</code> callback should now be defined like <code>Signal[int, str]</code> -- by <a href="https://github.com/Vizonex"><code>@Vizonex</code></a> and <a href="https://github.com/Dreamsorcerer"><code>@Dreamsorcerer</code></a>. <code>[aio-libs#699](aio-libs/aiosignal#699) <https://github.com/aio-libs/aiosignal/pulls/699></code><em>, <code>[aio-libs#710](aio-libs/aiosignal#710) <https://github.com/aio-libs/aiosignal/pulls/710></code></em></p> </li> </ul> <h2>Misc</h2> <ul> <li>Removed the sphinxcontrib-asyncio documentation dependency. <code>[aio-libs#528](aio-libs/aiosignal#528) <https://github.com/aio-libs/aiosignal/pull/528></code>_</li> </ul> <hr /> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aio-libs/aiosignal/commit/1cf80149c869d410c90a58e85e9c703be6ef8692"><code>1cf8014</code></a> Fix deploy</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/892494c5c72553e281e57e924cf055e6125fb0fc"><code>892494c</code></a> Release v1.4 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/718">#718</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/fa360821631383aed6a534da6f73ad149ec666f7"><code>fa36082</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/719">#719</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/b7f68f12fed7c4b84a6866984e7adafcd18fe265"><code>b7f68f1</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/717">#717</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/2b1acac380eaaa91a643bfc9c24fa1f3942f0d45"><code>2b1acac</code></a> Build(deps): Bump sigstore/gh-action-sigstore-python from 3.0.0 to 3.0.1 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/716">#716</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/17456ed5f968c0001a8823c2076f999fbf448157"><code>17456ed</code></a> Build(deps): Bump tox from 4.26.0 to 4.27.0 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/715">#715</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/4c236903da2e71b85652c07bed69013189a39406"><code>4c23690</code></a> Build(deps): Bump pytest from 8.4.0 to 8.4.1 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/714">#714</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/7be2f6833be08bb14207bc627f9931665cd947ce"><code>7be2f68</code></a> Build(deps): Bump mypy from 1.16.0 to 1.16.1 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/713">#713</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/5d62945d07c9413720e968cc3f25c66307d9a337"><code>5d62945</code></a> Build(deps): Bump coverage from 7.9.0 to 7.9.1 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/712">#712</a>)</li> <li><a href="https://github.com/aio-libs/aiosignal/commit/a6d85c1c3430621814d6163ea442828e7f31b34b"><code>a6d85c1</code></a> Build(deps): Bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 (<a href="https://redirect.github.com/aio-libs/aiosignal/issues/694">#694</a>)</li> <li>Additional commits viewable in <a href="https://github.com/aio-libs/aiosignal/compare/v1.3.2...v1.4.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 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> --------- (cherry picked from commit 9571860) <!-- Thank you for your contribution! --> ## What do these changes do? <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? <!-- Outline any notable behaviour for the end users. --> ## Is it a substantial burden for the maintainers to support this? <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> ## Related issue number <!-- Will this resolve any open issues? --> <!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes #123'). --> ## Checklist - [ ] I think the code is well written - [ ] Unit tests for the changes exist - [ ] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
pull bot
pushed a commit
that referenced
this pull request
Sep 11, 2025
aio-libs#11498) <!-- Thank you for your contribution! --> ## What do these changes do? Fixes the tests in sandboxed build environments where `/tmp` is not accessible. <!-- Please give a short brief about these changes. --> ## Are there changes in behavior for the user? No. <!-- Outline any notable behaviour for the end users. --> ## Is it a substantial burden for the maintainers to support this? Hopefully not: the fixture is used elsewhere in the tests for the same purpose. <!-- Stop right there! Pause. Just for a minute... Can you think of anything obvious that would complicate the ongoing development of this project? Try to consider if you'd be able to maintain it throughout the next 5 years. Does it seem viable? Tell us your thoughts! We'd very much love to hear what the consequences of merging this patch might be... This will help us assess if your change is something we'd want to entertain early in the review process. Thank you in advance! --> ## Related issue number <!-- Will this resolve any open issues? --> <!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes #123'). --> ## Checklist - [x] I think the code is well written - [x] Unit tests for the changes exist *(well, the change is to a unit test…)* - [x] Documentation reflects the changes - [ ] If you provide code modification, please add yourself to `CONTRIBUTORS.txt` *(patch is too trivial to even be copyrightable, I feel no need for credit beyond the commit log)* * The format is <Name> <Surname>. * Please keep alphabetical order, the file is sorted by names. - [ ] Add a new news fragment into the `CHANGES/` folder *(too trivial to changelog)* * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`) * if you don't have an issue number, change it to the pull request number after creating the PR * `.bugfix`: A bug fix for something the maintainers deemed an improper undesired behavior that got corrected to match pre-agreed expectations. * `.feature`: A new behavior, public APIs. That sort of stuff. * `.deprecation`: A declaration of future API removals and breaking changes in behavior. * `.breaking`: When something public is removed in a breaking way. Could be deprecated in an earlier release. * `.doc`: Notable updates to the documentation structure or build process. * `.packaging`: Notes for downstreams about unobvious side effects and tooling. Changes in the test invocation considerations and runtime assumptions. * `.contrib`: Stuff that affects the contributor experience. e.g. Running tests, building the docs, setting up the development environment. * `.misc`: Changes that are hard to assign to any of the above categories. * Make sure to use full sentences with correct case and punctuation, for example: ```rst Fixed issue with non-ascii contents in doctest text files -- by :user:`contributor-gh-handle`. ``` Use the past tense or the present tense a non-imperative mood, referring to what's changed compared to the last released version of this project.
pull bot
pushed a commit
that referenced
this pull request
Dec 2, 2025
Bumps [exceptiongroup](https://github.com/agronholm/exceptiongroup) from 1.3.0 to 1.3.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/releases">exceptiongroup's releases</a>.</em></p> <blockquote> <h2>1.3.1</h2> <ul> <li>Fixed <code>AttributeError: 'TracebackException' object has no attribute 'exceptions'</code> when formatting unpickled TBEs from another Python process which did not apply the <code>exceptiongroup</code> patches (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/144">#144</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/blob/main/CHANGES.rst">exceptiongroup's changelog</a>.</em></p> <blockquote> <h1>Version history</h1> <p>This library adheres to <code>Semantic Versioning 2.0 <http://semver.org/></code>_.</p> <p><strong>1.3.1</strong></p> <ul> <li>Fixed <code>AttributeError: 'TracebackException' object has no attribute 'exceptions'</code> when formatting unpickled TBEs from another Python process which did not apply the <code>exceptiongroup</code> patches (<code>[#144](agronholm/exceptiongroup#144) <https://github.com/agronholm/exceptiongroup/issues/144></code>_)</li> </ul> <p><strong>1.3.0</strong></p> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<code>[#143](agronholm/exceptiongroup#143) <https://github.com/agronholm/exceptiongroup/issues/143></code>_)</li> </ul> <p><strong>1.2.2</strong></p> <ul> <li>Removed an <code>assert</code> in <code>exceptiongroup._formatting</code> that caused compatibility issues with Sentry (<code>[#123](agronholm/exceptiongroup#123) <https://github.com/agronholm/exceptiongroup/issues/123></code>_)</li> </ul> <p><strong>1.2.1</strong></p> <ul> <li>Updated the copying of <code>__notes__</code> to match CPython behavior (PR by CF Bolz-Tereick)</li> <li>Corrected the type annotation of the exception handler callback to accept a <code>BaseExceptionGroup</code> instead of <code>BaseException</code></li> <li>Fixed type errors on Python < 3.10 and the type annotation of <code>suppress()</code> (PR by John Litborn)</li> </ul> <p><strong>1.2.0</strong></p> <ul> <li>Added special monkeypatching if <code>Apport <https://github.com/canonical/apport></code>_ has overridden <code>sys.excepthook</code> so it will format exception groups correctly (PR by John Litborn)</li> <li>Added a backport of <code>contextlib.suppress()</code> from Python 3.12.1 which also handles suppressing exceptions inside exception groups</li> <li>Fixed bare <code>raise</code> in a handler reraising the original naked exception rather than an exception group which is what is raised when you do a <code>raise</code> in an <code>except*</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ddddb6fdf8582c4ae5187dc1bd258115974229fe"><code>ddddb6f</code></a> Added the release version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/49c5e60d9efad1416f4f42455e119375904a1d6d"><code>49c5e60</code></a> Fixed AttributeError when formatting unpickled TBEs from an unpatched process</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/1be517f553249822a8fa12a4d7520d4b3ef15acd"><code>1be517f</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/152">#152</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/af0ea2fdfe218a4c2a1cb31ebd1a61dba459af6f"><code>af0ea2f</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/149">#149</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/7c980a88a06a72db3d796d98504b335d24274abb"><code>7c980a8</code></a> Removed pin on pyright version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ef853368c8b94479adbd33cc58f1cac05839e116"><code>ef85336</code></a> Fixed typing job not finding Python 3.14</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/080b3f4e925bbdb8cee70cc30c5ef2937eab2bde"><code>080b3f4</code></a> Pinned pyright version to fix typeshed related failure</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ac660908a1987880eddbb249947c1eef6e08513b"><code>ac66090</code></a> Added Python 3.14 to the test matrix</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/a0da94dadfb39c0b52c0cd5c87ace166b00f74c1"><code>a0da94d</code></a> Fixed test failures on Python 3.14</li> <li>See full diff in <a href="https://github.com/agronholm/exceptiongroup/compare/1.3.0...1.3.1">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>
pull bot
pushed a commit
that referenced
this pull request
Jan 3, 2026
Bumps [exceptiongroup](https://github.com/agronholm/exceptiongroup) from 1.3.0 to 1.3.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/releases">exceptiongroup's releases</a>.</em></p> <blockquote> <h2>1.3.1</h2> <ul> <li>Fixed <code>AttributeError: 'TracebackException' object has no attribute 'exceptions'</code> when formatting unpickled TBEs from another Python process which did not apply the <code>exceptiongroup</code> patches (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/144">#144</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/agronholm/exceptiongroup/blob/main/CHANGES.rst">exceptiongroup's changelog</a>.</em></p> <blockquote> <h1>Version history</h1> <p>This library adheres to <code>Semantic Versioning 2.0 <http://semver.org/></code>_.</p> <p><strong>1.3.1</strong></p> <ul> <li>Fixed <code>AttributeError: 'TracebackException' object has no attribute 'exceptions'</code> when formatting unpickled TBEs from another Python process which did not apply the <code>exceptiongroup</code> patches (<code>[#144](agronholm/exceptiongroup#144) <https://github.com/agronholm/exceptiongroup/issues/144></code>_)</li> </ul> <p><strong>1.3.0</strong></p> <ul> <li>Added <code>**kwargs</code> to function and method signatures as appropriate to match the signatures in the standard library</li> <li>In line with the stdlib typings in typeshed, updated <code>(Base)ExceptionGroup</code> generic types to define defaults for their generic arguments (defaulting to <code>BaseExceptionGroup[BaseException]</code> and <code>ExceptionGroup[Exception]</code>) (PR by <a href="https://github.com/mikenerone"><code>@mikenerone</code></a>)</li> <li>Changed <code>BaseExceptionGroup.__init__()</code> to directly call <code>BaseException.__init__()</code> instead of the superclass <code>__init__()</code> in order to emulate the CPython behavior (broken or not) (PR by <a href="https://github.com/cfbolz"><code>@cfbolz</code></a>)</li> <li>Changed the <code>exceptions</code> attribute to always return the same tuple of exceptions, created from the original exceptions sequence passed to <code>BaseExceptionGroup</code> to match CPython behavior (<code>[#143](agronholm/exceptiongroup#143) <https://github.com/agronholm/exceptiongroup/issues/143></code>_)</li> </ul> <p><strong>1.2.2</strong></p> <ul> <li>Removed an <code>assert</code> in <code>exceptiongroup._formatting</code> that caused compatibility issues with Sentry (<code>[#123](agronholm/exceptiongroup#123) <https://github.com/agronholm/exceptiongroup/issues/123></code>_)</li> </ul> <p><strong>1.2.1</strong></p> <ul> <li>Updated the copying of <code>__notes__</code> to match CPython behavior (PR by CF Bolz-Tereick)</li> <li>Corrected the type annotation of the exception handler callback to accept a <code>BaseExceptionGroup</code> instead of <code>BaseException</code></li> <li>Fixed type errors on Python < 3.10 and the type annotation of <code>suppress()</code> (PR by John Litborn)</li> </ul> <p><strong>1.2.0</strong></p> <ul> <li>Added special monkeypatching if <code>Apport <https://github.com/canonical/apport></code>_ has overridden <code>sys.excepthook</code> so it will format exception groups correctly (PR by John Litborn)</li> <li>Added a backport of <code>contextlib.suppress()</code> from Python 3.12.1 which also handles suppressing exceptions inside exception groups</li> <li>Fixed bare <code>raise</code> in a handler reraising the original naked exception rather than an exception group which is what is raised when you do a <code>raise</code> in an <code>except*</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ddddb6fdf8582c4ae5187dc1bd258115974229fe"><code>ddddb6f</code></a> Added the release version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/49c5e60d9efad1416f4f42455e119375904a1d6d"><code>49c5e60</code></a> Fixed AttributeError when formatting unpickled TBEs from an unpatched process</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/1be517f553249822a8fa12a4d7520d4b3ef15acd"><code>1be517f</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/152">#152</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/af0ea2fdfe218a4c2a1cb31ebd1a61dba459af6f"><code>af0ea2f</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/agronholm/exceptiongroup/issues/149">#149</a>)</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/7c980a88a06a72db3d796d98504b335d24274abb"><code>7c980a8</code></a> Removed pin on pyright version</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ef853368c8b94479adbd33cc58f1cac05839e116"><code>ef85336</code></a> Fixed typing job not finding Python 3.14</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/080b3f4e925bbdb8cee70cc30c5ef2937eab2bde"><code>080b3f4</code></a> Pinned pyright version to fix typeshed related failure</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/ac660908a1987880eddbb249947c1eef6e08513b"><code>ac66090</code></a> Added Python 3.14 to the test matrix</li> <li><a href="https://github.com/agronholm/exceptiongroup/commit/a0da94dadfb39c0b52c0cd5c87ace166b00f74c1"><code>a0da94d</code></a> Fixed test failures on Python 3.14</li> <li>See full diff in <a href="https://github.com/agronholm/exceptiongroup/compare/1.3.0...1.3.1">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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1)
Can you help keep this open source service alive? 💖 Please sponsor : )