fix: resolve include_extras parameter validation in resolve_dependencies
- Fix extra dependencies being filtered out by Python version checks - Add proper handling for extra markers in dependency parsing - Update parameter descriptions and documentation - Add comprehensive examples and demo script - Test with requests[socks], django[argon2,bcrypt], setuptools[test]
This commit is contained in:
parent
146952f404
commit
114a7d8d5a
6 changed files with 498 additions and 7 deletions
|
|
@ -35,7 +35,8 @@ class DependencyResolver:
|
|||
Args:
|
||||
package_name: Name of the package to resolve
|
||||
python_version: Target Python version (e.g., "3.10")
|
||||
include_extras: List of extra dependencies to include
|
||||
include_extras: List of extra dependency groups to include (e.g., ['socks'] for requests,
|
||||
['test', 'doc'] for setuptools). These are optional dependencies defined by the package.
|
||||
include_dev: Whether to include development dependencies
|
||||
max_depth: Maximum recursion depth (overrides instance default)
|
||||
|
||||
|
|
@ -242,7 +243,8 @@ async def resolve_package_dependencies(
|
|||
Args:
|
||||
package_name: Name of the package to resolve
|
||||
python_version: Target Python version (e.g., "3.10")
|
||||
include_extras: List of extra dependencies to include
|
||||
include_extras: List of extra dependency groups to include (e.g., ['socks'] for requests,
|
||||
['test', 'doc'] for setuptools). These are optional dependencies defined by the package.
|
||||
include_dev: Whether to include development dependencies
|
||||
max_depth: Maximum recursion depth
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue