Comments (3)
To add, from here:
Currently, deptry
contains some potentially confusing behavior. When python-dotenv
is in the dependencies, but not installed (so it has no metadata), with the following configuration:
[tool.deptry.package_module_name_map]
python-dotenv = [
"dotenv",
]
a warning is still shown:
Warning: Package 'python-dotenv' not found in current environment. Assuming its corresponding module name is 'python_dotenv'.
I think this is now undesired behavior? As a user I would expect that, since I manually specified which module I want the dependency to map to, I do not expect to see a warning, since I already specified how I want this package to be dealt with.
from deptry.
Note that the warning is actually not necessarily correct. The Assuming its corresponding module name is 'python_dotenv'
part is not a consequence of not finding the metadata. It 's a consequence of (always) adding the translation to the top level module name set.
Whether or not to add the translated package name should be discussed in #335.
Given that, I think the warning message could be improved by removing the part mentioned above.
Furthermore, as property found
is currently unused, you may decide to remove it, eliminating the metadata lookup when pre-configured top level module names are set for a package.
from deptry.
I've added #337 as an example solution.
from deptry.
Related Issues (20)
- Release 0.10.0 HOT 7
- Replace the word 'obsolete' with 'unused' HOT 2
- How to use the tool when no virtual environment is being used? HOT 2
- Output action items for users when some dependency issues are found HOT 1
- Release 0.11.0 HOT 1
- Retrieve development dependencies from all dependencies groups in Poetry HOT 2
- Replace `--ignore-*` flags with `select` (and optionally `ignore`.) HOT 2
- Potential DEP005: Detect Poetry `extras` that are not listed under dependencies. HOT 3
- The CommaSeparatedTupleParamType's error is too specific
- Determine naming convention for issues/violations/errors/checks HOT 3
- Python-* and *-python named packages are not well recognized HOT 8
- pre-commit hook requires deptry to be globally installed HOT 2
- KeyError when pyproject.toml dependencies are dynamically read from requirements.txt HOT 2
- Release 0.12.0 HOT 2
- Feature Request Summary
- Support for Django HOT 5
- [Feature Request] `--config` relative to `root` HOT 1
- Allow optional dependencies to be detected HOT 3
- Auto-generated regular expressions HOT 1
- The pre-commit hook should only lint staged files
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from deptry.