[pull] master from aio-libs:master #98
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
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #98 +/- ##
=========================================
Coverage ? 98.74%
=========================================
Files ? 122
Lines ? 36956
Branches ? 4411
=========================================
Hits ? 36494
Misses ? 315
Partials ? 147
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
pull bot
pushed a commit
that referenced
this pull request
Jan 7, 2026
Bumps [pathspec](https://github.com/cpburnz/python-pathspec) from 0.12.1 to 1.0.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/cpburnz/python-pathspec/releases">pathspec's releases</a>.</em></p> <blockquote> <h2>v1.0.1</h2> <p>Release v1.0.1. See <a href="https://github.com/cpburnz/python-pathspec/blob/v1.0.1/CHANGES.rst">CHANGES.rst</a>.</p> <h2>v1.0.0</h2> <p>Release v1.0.0. See <a href="https://github.com/cpburnz/python-pathspec/blob/v1.0.0/CHANGES.rst">CHANGES.rst</a>.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/cpburnz/python-pathspec/blob/master/CHANGES.rst">pathspec's changelog</a>.</em></p> <blockquote> <h2>1.0.1 (2026-01-06)</h2> <p>Bug fixes:</p> <ul> <li><code>Issue [#100](https://github.com/cpburnz/python-pathspec/issues/100)</code>_: ValueError(f"{patterns=!r} cannot be empty.") when using black.</li> </ul> <p>.. _<code>Issue [#100](https://github.com/cpburnz/python-pathspec/issues/100)</code>: <a href="https://redirect.github.com/cpburnz/python-pathspec/issues/100">cpburnz/python-pathspec#100</a></p> <h2>1.0.0 (2026-01-05)</h2> <p>Major changes:</p> <ul> <li><code>Issue [#91](https://github.com/cpburnz/python-pathspec/issues/91)</code>_: Dropped support of EoL Python 3.8.</li> <li>Added concept of backends to allow for faster regular expression matching. The backend can be controlled using the <code>backend</code> argument to <code>PathSpec()</code>, <code>PathSpec.from_lines()</code>, <code>GitIgnoreSpec()</code>, and <code>GitIgnoreSpec.from_lines()</code>.</li> <li>Renamed "gitwildmatch" pattern back to "gitignore". The "gitignore" pattern behaves slightly differently when used with <code>PathSpec</code> (<em>gitignore</em> as documented) than with <code>GitIgnoreSpec</code> (replicates <em>Git</em>'s edge cases).</li> </ul> <p>API changes:</p> <ul> <li>Breaking: protected method <code>pathspec.pathspec.PathSpec._match_file()</code> (with a leading underscore) has been removed and replaced by backends. This does not affect normal usage of <code>PathSpec</code> or <code>GitIgnoreSpec</code>. Only custom subclasses will be affected. If this breaks your usage, let me know by <code>opening an issue <https://github.com/cpburnz/python-pathspec/issues></code>_.</li> <li>Deprecated: "gitwildmatch" is now an alias for "gitignore".</li> <li>Deprecated: <code>pathspec.patterns.GitWildMatchPattern</code> is now an alias for <code>pathspec.patterns.gitignore.spec.GitIgnoreSpecPattern</code>.</li> <li>Deprecated: <code>pathspec.patterns.gitwildmatch</code> module has been replaced by the <code>pathspec.patterns.gitignore</code> package.</li> <li>Deprecated: <code>pathspec.patterns.gitwildmatch.GitWildMatchPattern</code> is now an alias for <code>pathspec.patterns.gitignore.spec.GitIgnoreSpecPattern</code>.</li> <li>Deprecated: <code>pathspec.patterns.gitwildmatch.GitWildMatchPatternError</code> is now an alias for <code>pathspec.patterns.gitignore.GitIgnorePatternError</code>.</li> <li>Removed: <code>pathspec.patterns.gitwildmatch.GitIgnorePattern</code> has been deprecated since v0.4 (2016-07-15).</li> <li>Signature of method <code>pathspec.pattern.RegexPattern.match_file()</code> has been changed from <code>def match_file(self, file: str) -> RegexMatchResult | None</code> to <code>def match_file(self, file: AnyStr) -> RegexMatchResult | None</code> to reflect usage.</li> <li>Signature of class method <code>pathspec.pattern.RegexPattern.pattern_to_regex()</code> has been changed from <code>def pattern_to_regex(cls, pattern: str) -> tuple[str, bool]</code> to <code>def pattern_to_regex(cls, pattern: AnyStr) -> tuple[AnyStr | None, bool | None]</code> to reflect usage and documentation.</li> </ul> <p>New features:</p> <ul> <li>Added optional "hyperscan" backend using <code>hyperscan</code>_ library. It will automatically be used when installed. This dependency can be installed with <code>pip install 'pathspec[hyperscan]'</code>.</li> <li>Added optional "re2" backend using the <code>google-re2</code>_ library. It will automatically be used when installed. This dependency can be installed with <code>pip install 'pathspec[re2]'</code>.</li> <li>Added optional dependency on <code>typing-extensions</code>_ library to improve some type hints.</li> </ul> <p>Bug fixes:</p> <ul> <li><code>Issue [#93](https://github.com/cpburnz/python-pathspec/issues/93)</code>_: Do not remove leading spaces.</li> <li><code>Issue [#95](https://github.com/cpburnz/python-pathspec/issues/95)</code>_: Matching for files inside folder does not seem to behave like .gitignore's.</li> <li><code>Issue [#98](https://github.com/cpburnz/python-pathspec/issues/98)</code>_: UnboundLocalError in RegexPattern when initialized with <code>pattern=None</code>.</li> <li>Type hint on return value of <code>pathspec.pattern.RegexPattern.match_file()</code> to match documentation.</li> </ul> <p>Improvements:</p> <ul> <li>Mark Python 3.13 and 3.14 as supported.</li> <li>No-op patterns are now filtered out when matching files, slightly improving performance.</li> <li>Fix performance regression in <code>iter_tree_files()</code> from v0.10.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/cpburnz/python-pathspec/commit/75f4d0672305dfe3d0a6f182b870c3edec29f316"><code>75f4d06</code></a> Release v1.0.1</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/3d942b5e2d00fd757593d89bf8c8b2ff2d6028b4"><code>3d942b5</code></a> Fix publish</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/6bcf1511216892e2290bc2f205115c42552cbabe"><code>6bcf151</code></a> Allow empty pattern list</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/24374bee15a7144558e7d84756b674ea61a0e73d"><code>24374be</code></a> Allow empty pattern list</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/3a946678cbf0b634ee7a9b94447b315a7b69cddd"><code>3a94667</code></a> Release v1.0.0</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/c8750218560b9c157c010e9339f3ba529bf79804"><code>c875021</code></a> Prepare for v1</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/5ab7e605f51a78fb126cad9f08b23fcc6c113a94"><code>5ab7e60</code></a> Prepare for v1</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/bc81a7dbd7bcaa1173d4d4fc20014237782fc5b1"><code>bc81a7d</code></a> PyPI</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/8869cbf092ab2262d7957698dc6e09602cf9ab23"><code>8869cbf</code></a> Misc</li> <li><a href="https://github.com/cpburnz/python-pathspec/commit/fcdf4770d474e24780e1d668a978c2f76a835df6"><code>fcdf477</code></a> TestPyPI</li> <li>Additional commits viewable in <a href="https://github.com/cpburnz/python-pathspec/compare/v0.12.1...v1.0.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
2 participants
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 : )