You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for Python 3.7 has been dropped in #352, given that it will reach end of life soon, and that PyPI stats show a really low usage of it. If you are using deptry on Python 3.7, consider upgrading to 3.8, or staying on <0.9.0.
Behaviour changes in package name guessing
In case packages don't provide the Python modules they expose, deptry tries to guess the package name by converting - to _, as a best effort, and warns about it in the logs. Before #337, deptry always guessed the module name, regardless of if the package provided the necessary information or not. Now, it will only guess the module name if the package does not provide the information and no mapping has been provided using the new --package-module-name-map flag (or package_module_name_map option in pyproject.toml).
Handling modules without __init__.py
With #285, deptry will now consider the following things as local modules:
directories without __init__.py (and at least one Python file)
single Python files
Previously, deptry only considered directories as local modules if an __init__.py was present, and did not account for cases where a single Python file could also be a local module, alongside directories.
Updated the changelog with the latest PRs that got merged, and added a Breaking changes section. Tell me what you think @fpgmaas. Once we are good with the changelog, I'll tag the new release.
Now, it will only guess the module name if the package does not provide the information.
to
Now, it will only guess the module name if the package does not provide the information and no mapping has been provided using the new --package-module-name-map flag (or package_module_name_map option in pyproject.toml).
Changelog for 0.9.0.
What's Changed
Breaking changes
Python 3.7 support dropped
Support for Python 3.7 has been dropped in #352, given that it will reach end of life soon, and that PyPI stats show a really low usage of it. If you are using
deptry
on Python 3.7, consider upgrading to 3.8, or staying on<0.9.0
.Behaviour changes in package name guessing
In case packages don't provide the Python modules they expose,
deptry
tries to guess the package name by converting-
to_
, as a best effort, and warns about it in the logs. Before #337,deptry
always guessed the module name, regardless of if the package provided the necessary information or not. Now, it will only guess the module name if the package does not provide the information and no mapping has been provided using the new--package-module-name-map
flag (orpackage_module_name_map
option inpyproject.toml
).Handling modules without
__init__.py
With #285,
deptry
will now consider the following things as local modules:__init__.py
(and at least one Python file)Previously,
deptry
only considered directories as local modules if an__init__.py
was present, and did not account for cases where a single Python file could also be a local module, alongside directories.Features
__init__.py
by @mkniewallner in feat(core): handle local modules without__init__.py
#285Bug Fixes
Miscellaneous
Full Changelog: 0.8.0...0.9.0
The text was updated successfully, but these errors were encountered: