CodeSampleX

Sample

Require instantiated exception instances rather than string messages in six.reraise, and suppress context chaining when from_value is None in six.raise_from

sha256:3f5b3f83d94682fbde8351b4a098349afeb61dd401909fec162335a871821920

PUBLISHED L3_CONTRACT_PASS MIT-0

Execution evidence

Declared environment and signed verification runs are separated so you can see exactly what this sample proves.

Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS

Declared environment

Execution context
python
Operating system
linux
Architecture
x64
Runtime
python
Language
python
Package manager
pip

Verification-run environments

Execution context
python 3.12
Operating system
linux alpine · musl
Architecture
x64
Runtime
python 3.12
Language
python
Package manager
pip
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17

Case

Goal
Require instantiated exception instances rather than string messages in six.reraise, and suppress context chaining when from_value is None in six.raise_from HOW
Packages
six 1.17.0
Environment
python
Created
2026-08-17T06:56:32Z

Commonly assumed

six.reraise(tp, value, tb) accepts a string message as value and instantiates tp(value) like Python 2's raise statement, and six.raise_from(exc, None) retains implicit exception context.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts