Skip to content

fix(python): stop suggesting the legacy wheel for optional Protect tracing - #722

Open
nik13 wants to merge 1 commit into
devfrom
docs/evaluator-install-guidance
Open

nik13 wants to merge 1 commit into
devfrom
docs/evaluator-install-guidance

Conversation

@nik13

@nik13 nik13 commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

When fi.evals.Protect cannot be imported, the Python instrumentors currently identify ai-evaluation as missing. Some of them ask the user to install that distribution. The import does not tell us which distribution supplied the module. Name the unavailable optional feature instead, without changing the logging level, instrumentor behavior or default install.

The Python guide directs new evaluation projects to an isolated Agent Learning Kit environment, and distinguishes it from existing [evaluation] installs. This is not a dependency rename: released fi-instrumentation-otel[evaluation]==1.5.0 also installs futureagi. Substituting the released kit would leave a fi/ wheel-file ownership conflict between agent-learning-kit==0.3.7 and futureagi==0.7.0. That compatibility issue needs a separate packaging decision. No historical releases, extras or platform SDK code are changed here.

Verification: parsed every modified Python file; apart from the 15 diagnostic string literals, the ASTs are identical to the base. git diff --check passed. Independent published-wheel test on GCP verified the standalone local metric and reproduced the two installation-order conflict; no hosted inference was tested. Awaiting repo CI.

🤖 Generated with Claude Code

…acing

Co-Authored-By: Claude Code <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant