Closed abingham closed 5 years ago
The point being that CosmicRayTestingException
is not something we can rely on now. Interesting...
I've disabled this operator for now until we can find a way to do it correctly.
One approach would be to use sitecustomize.py
. It could modify __builtins__
to add CosmicRayTestingException
.
Would this potentially conflict with the user's sitecustomize? Not with the current cloning technologies; we don't do anything that could put a sitecustomize in place. So this might work cleanly.
Fixed in 7bee55663608fa893a406bfa648e22521287fa49.
We use sitecustomize.py
for the actually test execution. We use a standard module for working with our custom exception type everywhere else.
We need to rethink our exception-replacement operator. We used to be able to rely on being able to inject a new exception type into the testing environment. Now we can't. See the following cr-html results as an example.