Correctly define packages and dependencies #571
Merged
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.
Ok so in #566 I have
gco main -- pyproject.toml
to restore the broken config spec.Ever since it was merged, somehow
pyproject.toml
was (accidentally?) reverted (again) to an incorrect state where "packages" was listed under build specifications, so my changes are not there.Changes
__init__.py
files to all package directories:agentops/llms/__init__.py
agentops/llms/providers/__init__.py
agentops/partners/__init__.py
pyproject.toml
to only specify root packageci
back to[dependency-groups]
Why
I made these changes to solve two issues:
__init__.py
files:We were explicitly listing every subpackage in
pyproject.toml
, which, according to the way it was done, it meant requiring manual updates whenever we add new directories (??)ci
group landed under "extras" again and it would make the tach pipeline fail again.References:
Important note:
The build specification section should only declare the root package. Do not modify it!