Update dependency version constraints in pyproject.toml#71
Update dependency version constraints in pyproject.toml#71rostamiiamz wants to merge 1 commit intoawslabs:devfrom
Conversation
| "ruff>=0.14.10", | ||
| ] | ||
| llm = [ | ||
| "strands-agents>=1.0.0,<=1.16.0" |
There was a problem hiding this comment.
Does LLM not need strands agents anymore? Also... beautifulsoup...doesn't that go in...dev?
There was a problem hiding this comment.
-
Should I keep the
llmoptional dependency group withstrands-agents? Does the project still need LLM functionality? -
Should
beautifulsoup4stay in dev dependencies, or does it belong in main dependencies or a different optional group?
There was a problem hiding this comment.
Just double check what is currently in dev, and then make sure that no dependencies are lost...whatever state it is in now.
Estimating what would happen with this change...if someone tried to install the llm dependency group... it wouldn't be there anymore...and strands-agents wouldn't be there either. So one goal would definitely be not to lose any functionality as a result of the addition.
Changes
jinja2dependency from main dependenciesrufffrom dev dependenciesllmoptional dependency groupMotivation
These changes improve dependency flexibility and reduce potential version conflicts when installing the package.