chore(deps-dev): bump deptry from 0.13.0 to 0.14.0

[dependabot]

Bumps deptry from 0.13.0 to 0.14.0.

Release notes

Sourced from deptry's releases.

0.14.0

What's Changed

This release significantly improves the speed of deptry, particularly for large projects, by utilizing Rust to manage the parsing of Abstract Syntax Trees (AST) from .py files and to extract the import statements. For some benchmarks, see below:

Changes

Since the changes are all in the back-end, little has changed for the user other than the execution speed. The two minor notable changes are:

• Improved identification of column identifier in imports detection. Where earlier the column identifier for an imported module foo in the line import foo would be 0, it now points to column 8.
• When a file can not be read, the error will be slightly more verbose and include the source file and line pointing to the location in deptry's source code responsible for logging the warning. So instead of Warning: File file1.py could not be read. Skipping..., the error will now read WARNING deptry.imports:imports.rs:66 Warning: File file1.py could not be read. Skipping.... This will likely be reverted in the future.

Available wheels on PyPi

Where earlier releases published a single .whl file to PyPi, with the move to Rust we now build and publish wheels for a variety of platforms and architectures. More specifically, wheel files for the following combinations are now available on PyPi:

• Linux: ABI3 wheels for x86_64 and aarch64 architectures.
• Windows: ABI3 wheels for the x64 architecture.
• macOS: ABI3 wheels for x86_64 and aarch64 (Apple Silicon) architectures.

Alongside the ABI3 wheels, we provide a source distribution (sdist) package.

Full Changelog: fpgmaas/deptry@0.13.0...0.14.0

0.14.0a1

This release speeds up deptry significantly, especially on large projects, by leveraging Rust to handle the parsing of the Abstract Syntax Trees (AST) from .py files and the extraction of import statements.

What's Changed

• WIP: Import extraction with Rust by @​fpgmaas in fpgmaas/deptry#581

Full Changelog: fpgmaas/deptry@0.13.0...0.14.0a1

Changelog

Sourced from deptry's changelog.

0.14.0 - 2024-03-14

This release significantly improves the speed of deptry, particularly for large projects, by utilizing Rust to manage the parsing of Abstract Syntax Trees (AST) from .py files and to extract the import statements. For some benchmarks, see below:

Changes

Since the changes are all in the back-end, little has changed for the user other than the execution speed. The two minor notable changes are:

• Improved identification of column identifier in imports detection. Where earlier the column identifier for an imported module foo in the line import foo would be 0, it now points to column 8.
• When a file can not be read, the error will be slightly more verbose and include the source file and line pointing to the location in deptry's source code responsible for logging the warning. So instead of Warning: File file1.py could not be read. Skipping..., the error will now read WARNING deptry.imports:imports.rs:66 Warning: File file1.py could not be read. Skipping.... This will likely be reverted in the future.

Available wheels on PyPi

Where earlier releases published a single .whl file to PyPi, with the move to Rust we now build and publish wheels for a variety of platforms and architectures. More specifically, wheel files for the following combinations are now available on PyPi:

• Linux: ABI3 wheels for x86_64 and aarch64 architectures.
• Windows: ABI3 wheels for the x64 architecture.
• macOS: ABI3 wheels for x86_64 and aarch64 (Apple Silicon) architectures.

Alongside the ABI3 wheels, we provide a source distribution (sdist) package.

Full Changelog: fpgmaas/deptry@0.13.0...0.14.0

Commits

• 8e002b7 chore(deps): update codecov/codecov-action action to v4 (#562)
• 78ace96 Small fix in the docs (#586)
• a13add1 WIP: Import extraction with Rust (#581)
• See full diff in compare view

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 commands and options

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)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[edgarrmondragon]

@dependabot merge