Fix OpenTelemetry dependency conflicts with autogen-core#638
Merged
Conversation
9b8f424 to
44e74fb
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Flags with carried forward coverage won't be shown. Click here to find out more. |
Contributor
Author
|
tested this with python 3.9 and 3.13 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
Users attempting to use
agentopsalongsideautogen-core==0.4.0encounter dependency resolution errors due to conflicting OpenTelemetry version requirements. This occurs because:agentopssupports Python ≥3.9 and uses OpenTelemetry 1.22.0autogen-core==0.4.0requires Python ≥3.10 and needs OpenTelemetry ≥1.27.0Solution
Added version-specific OpenTelemetry constraints in
pyproject.tomlto handle both scenarios:This ensures:
agentopsalongsideautogen-corewithout conflictsTesting
Verified dependency resolution works in both scenarios:
No changes to core functionality or API.