Remove transitive dependencies and update requirements #162
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.
As part of our ongoing research on Python dependency management, we identified that your project explicitly declares the dependencies
certifiandidna, which are not directly used by the project codebase but are required transitively by higher-level packages such asrequests,httpx,aiohttp,elastic-transport,py2neo, and others.These packages are pulled in automatically through primary dependencies and do not need to be declared explicitly. Keeping such transitive dependencies locked in
dev/tests-requirements.txtintroduces unnecessary version constraints and increases maintenance overhead.We verified that after removing these dependencies, the project continues to install and function properly, and the test suite passes successfully. This confirms that the removed packages are not directly used in the codebase.
For reference, this change aligns with best practices described in the pip documentation, which encourages auditing and pruning transitive or unused requirements to simplify the dependency graph and reduce the risk of version pinning issues.