dependabot[bot] opened a new pull request, #649:
URL: https://github.com/apache/iceberg-python/pull/649

   Bumps [deptry](https://github.com/fpgmaas/deptry) from 0.14.0 to 0.16.1.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/fpgmaas/deptry/releases";>deptry's 
releases</a>.</em></p>
   <blockquote>
   <h2>0.16.1</h2>
   <h2>What's Changed</h2>
   <h3>Bug Fixes</h3>
   <ul>
   <li>Skip type checking blocks whether future annotations are used or not (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/662";>#662</a>)</li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/fpgmaas/deptry/compare/0.16.0...0.16.1";>https://github.com/fpgmaas/deptry/compare/0.16.0...0.16.1</a></p>
   <h2>0.16.0</h2>
   <h2>What's Changed</h2>
   <h3>Breaking changes</h3>
   <h4><code>typing.TYPE_CHECKING</code> handling</h4>
   <p>Imports guarded by <code>typing.TYPE_CHECKING</code> when using 
<code>from __future__ import annotations</code> are now skipped. For 
instance:</p>
   <pre lang="python"><code>from __future__ import annotations
   <p>from typing import TYPE_CHECKING</p>
   <p>if TYPE_CHECKING:
   # This import will not be extracted as it is guarded by 
<code>TYPE_CHECKING</code> and <code>from __future__ import annotations</code>
   # is used. This means the import should only be evaluated by type checkers, 
and should not be evaluated during runtime.
   import mypy_boto3_s3
   </code></pre></p>
   <p>See <a 
href="https://deptry.com/usage/#imports-extraction";>https://deptry.com/usage/#imports-extraction</a>
 for more information.</p>
   <h4><code>requirements.in</code> handling</h4>
   <p>On projects using <code>pip</code> requirements format for defining 
dependencies, if <code>requirements_files</code> option is not overridden,
   <em>deptry</em> will first search for a <code>requirements.in</code> file 
before <code>requirements.txt</code>, to better support projects using
   <code>pip-tools</code> and the like (which includes <code>uv</code> and Rye) 
out of the box. If you use <code>requirements.in</code> and want 
<em>deptry</em> to
   use <code>requirements.txt</code>, you can either pass 
<code>--requirements-files requirements.txt</code> when invoking 
<em>deptry</em>, or set the
   option in <code>pyproject.toml</code>:</p>
   <pre lang="toml"><code>[tool.deptry]
   requirements_files = [&quot;requirements.txt&quot;]
   </code></pre>
   <h3>Features</h3>
   <ul>
   <li>Skip type checking blocks when parsing imports (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/652";>#652</a>)</li>
   <li>Search for <code>requirements.in</code> before 
<code>requirements.txt</code> on projects using <code>pip</code> requirements 
format for dependencies (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/641";>#641</a>)</li>
   </ul>
   <h3>Bug Fixes</h3>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/fpgmaas/deptry/blob/main/CHANGELOG.md";>deptry's 
changelog</a>.</em></p>
   <blockquote>
   <h2>0.16.1 - 2024-04-06</h2>
   <h3>Bug Fixes</h3>
   <ul>
   <li>Skip type checking blocks whether future annotations are used (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/662";>#662</a>)</li>
   </ul>
   <h3>Full Changelog</h3>
   <p><a 
href="https://github.com/fpgmaas/deptry/compare/0.16.0...0.16.1";>https://github.com/fpgmaas/deptry/compare/0.16.0...0.16.1</a></p>
   <h2>0.16.0 - 2024-04-04</h2>
   <h3>Breaking changes</h3>
   <h4><code>typing.TYPE_CHECKING</code> handling</h4>
   <p>Imports guarded by <code>typing.TYPE_CHECKING</code> when using 
<code>from __future__ import annotations</code> are now skipped. For 
instance:</p>
   <pre lang="python"><code>from __future__ import annotations
   <p>from typing import TYPE_CHECKING</p>
   <p>if TYPE_CHECKING:</p>
   <h1>This import will not be extracted as it is guarded by 
<code>TYPE_CHECKING</code> and <code>from __future__ import 
annotations</code></h1>
   <h1>is used. This means the import should only be evaluated by type 
checkers, and should not be evaluated during runtime.</h1>
   <p>import mypy_boto3_s3
   </code></pre></p>
   <p>See <a 
href="https://deptry.com/usage/#imports-extraction";>https://deptry.com/usage/#imports-extraction</a>
 for more information.</p>
   <h4><code>requirements.in</code> handling</h4>
   <p>On projects using <code>pip</code> requirements format for defining 
dependencies, if <code>requirements_files</code> option is not overridden,
   <em>deptry</em> will first search for a <code>requirements.in</code> file 
before <code>requirements.txt</code>, to better support projects using
   <code>pip-tools</code> and the like (which includes <code>uv</code> and Rye) 
out of the box. If you use <code>requirements.in</code> and want 
<em>deptry</em> to
   use <code>requirements.txt</code>, you can either pass 
<code>--requirements-files requirements.txt</code> when invoking 
<em>deptry</em>, or set the
   option in <code>pyproject.toml</code>:</p>
   <pre lang="toml"><code>[tool.deptry]
   requirements_files = [&quot;requirements.txt&quot;]
   </code></pre>
   <h3>Features</h3>
   <ul>
   <li>Skip type checking blocks when parsing imports (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/652";>#652</a>)</li>
   <li>Search for <code>requirements.in</code> before 
<code>requirements.txt</code> on projects using <code>pip</code> requirements 
format for
   dependencies (<a 
href="https://redirect.github.com/fpgmaas/deptry/pull/641";>#641</a>)</li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/caa4e436cca5b15c1e63488f8594050cb21488d0";><code>caa4e43</code></a>
 docs(changelog): add 0.16.1 release notes (<a 
href="https://redirect.github.com/fpgmaas/deptry/issues/668";>#668</a>)</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/15c344a10d0295f74cab4ac19aa69972ffffd5b5";><code>15c344a</code></a>
 chore(deps): lock file maintenance</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/a2bfd61e824167fc7b5b5179dc597ca3af0240c0";><code>a2bfd61</code></a>
 fix(deps): update rust crate serde_json to 1.0.115</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/d533f053e998377a60562fb3b670f24a7c194346";><code>d533f05</code></a>
 chore(deps): update dependency docs/mkdocs-material to v9.5.17</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/e187ac97f5b471a56655ec349ddfae072b564358";><code>e187ac9</code></a>
 fix(deps): update rust crate rayon to 1.10.0</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/ece7c1a07342a6f42b671a37009bda5fbeefd212";><code>ece7c1a</code></a>
 chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.3.5</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/1fa8170842b32c7f6e70827eb244cb7a0a2b24ea";><code>1fa8170</code></a>
 fix(visitor): skip type checking blocks without future annotations (<a 
href="https://redirect.github.com/fpgmaas/deptry/issues/662";>#662</a>)</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/36a06f08a00941320d817149a8230d5cec297b55";><code>36a06f0</code></a>
 docs(changelog): add 0.16.0 release notes (<a 
href="https://redirect.github.com/fpgmaas/deptry/issues/657";>#657</a>)</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/2ac789fe8ac0db98521f716f429113be42dcdbc9";><code>2ac789f</code></a>
 Automatically use <code>requirements.in</code> if the project uses a 
<code>requirements.txt</code> ...</li>
   <li><a 
href="https://github.com/fpgmaas/deptry/commit/714596cc3494185cbdf5b2151fce832b6010def9";><code>714596c</code></a>
 ci: tweak workflows (<a 
href="https://redirect.github.com/fpgmaas/deptry/issues/658";>#658</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/fpgmaas/deptry/compare/0.14.0...0.16.1";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=deptry&package-manager=pip&previous-version=0.14.0&new-version=0.16.1)](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>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to