Python wrapper and version management tool for the solc Solidity compiler.
77
Evaluation — 77%
↑ 1.05xAgent success when using this tile
{
"context": "Evaluates whether the solution uses py-solc-x to compile Solidity files from disk with import remappings, producing ABI and bytecode outputs and persisting compiler artifacts. Emphasizes correct use of remapping, allow-path, and output controls, plus clear error propagation for unresolved imports.",
"type": "weighted_checklist",
"checklist": [
{
"name": "compile_files call",
"description": "Invokes py-solc-x `compile_files` (not `compile_source`) with the provided on-disk Solidity paths so the compiler resolves imports relative to the filesystem.",
"max_score": 35
},
{
"name": "Import remappings",
"description": "Passes the user-provided mapping to the `import_remappings` argument (e.g., \"@lib/=vendor/lib/\") so remapped library imports resolve during compilation.",
"max_score": 25
},
{
"name": "Allow/base paths",
"description": "Sets `base_path` or `allow_paths` in the `compile_files` call to include the entry and remapped library directories, matching the spec’s allow-path requirement.",
"max_score": 15
},
{
"name": "Output artifacts",
"description": "Requests ABI and bytecode via `output_values` or `output_selection` and uses `output_dir`/`overwrite` in `compile_files` so combined JSON artifacts are written to the specified directory.",
"max_score": 15
},
{
"name": "Error surfacing",
"description": "Surfaces `SolcError` details when compilation fails, ensuring unresolved import paths appear in the raised error message instead of being swallowed or replaced.",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/pypi-py-solc-xevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10