The documented import for `assert_output_satisfies` raises `ImportError`

Open Beginner friendly
#502 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start with src/conductor/ai/agents/testing/semantic.py and src/conductor/ai/agents/testing/init.py, especially the documented import and the all section at lines 61-97. Reproduce the failure with the Python command in the issue, then verify the chosen documentation or export behavior with the relevant testing package checks. Done means the documented import is consistent with the supported public API.

Written by the indexing model from the issue text.

Description

Bug Description

The import shown in semantic.py's own module docstring fails.

Root Cause

src/conductor/ai/agents/testing/semantic.py:9 documents
from conductor.ai.agents.testing import assert_output_satisfies, but testing/__init__.py
never imports semantic and the name is absent from __all__ (__init__.py:61-97).

Steps to Reproduce

python -c "from conductor.ai.agents.testing import assert_output_satisfies"
# ImportError

Expected Behavior

Either add the re-export or correct the docstring. The re-export looks like the intent, since
every other assertion in the package is exposed that way. Working import today is
from conductor.ai.agents.testing.semantic import assert_output_satisfies.

Additional Notes

Verified against origin/main @ c99e2cf9. Found while reading the module; unrelated to the
tool-call and event defects filed separately.

Dominant language
Python
Stars
104
Forks
43
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from conductor-oss/python-sdk

All issues in conductor-oss/python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.