chore: Remove dead Python eval tooling#1070
Merged
Merged
Conversation
What we're solving: pyproject.toml (package apify-mcp-evals, full ruff config) and notebooks/evaluation_2025.ipynb are leftovers from an old Python-based eval setup. The eval harness is TypeScript today (evals/*.ts), so pyproject.toml governs zero .py files, and the notebook's results already live in Phoenix cloud. Both mislead anyone browsing the repo. How: git rm both files. No source edits; nothing in the repo references either file, so runtime behavior is unchanged. Alternatives considered: keep pyproject.toml as a placeholder for future Python tooling (rejected — none exists or is planned); archive the notebook elsewhere (rejected — results are already in Phoenix cloud). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016pXZvhEoE6Lz3DpBSL3n1Y
9 tasks
RobertCrupa
approved these changes
Jul 10, 2026
RobertCrupa
left a comment
RobertCrupa
left a comment
Contributor
There was a problem hiding this comment.
So satisfying to see all red, no green 🚀
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
4 participants
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.
Part of #1066 (checkbox: remove dead Python tooling).
What we're solving
pyproject.toml(packageapify-mcp-evals, full ruff config) andnotebooks/evaluation_2025.ipynbare leftovers from an old Python-based eval setup. The eval harness is TypeScript today (evals/*.ts), sopyproject.tomlgoverns zero.pyfiles, and the notebook's results already live in Phoenix cloud. Both mislead anyone browsing the repo into thinking Python tooling exists.How
git rmboth files. No source edits — nothing in the repo (source, CI workflows,package.json, docs) references either file, so runtime behavior is unchanged.Alternatives considered
pyproject.tomlas a placeholder for future Python tooling — rejected; none exists or is planned.Notes
.gitignorePython-cache lines (__pycache__/,.venv) left alone — separate, unrelated cleanup.Verification
type-checkclean,lint0 errors,check:agentspassed,test:unit959 passed / 2 skipped,formatno-op.git grep).🤖 Generated with Claude Code
https://claude.ai/code/session_016pXZvhEoE6Lz3DpBSL3n1Y
Generated by Claude Code