Change panic behavior to the default of unwind

[jtran]

Related: #10121.

The primary motivation of this is so that Python code using the bindings can catch any panics in the Rust code, rather than the panic aborting the process.

• Test to verify it actually raises PanicException. I did this locally, but I don't think it's worth committing since it requires triggering a panic. Also, I learned that for async Rust, we handle it and raise Exception instead. But it's not guaranteed, so it's good to catch PanicException also.

  modeling-app/rust/kcl-python-bindings/src/lib.rs

  Line 47 in 092129a

  .map_err(|err| PyException::new_err(err.to_string()))?

Note: wasm32-unknown-unknown doesn't currently implement unwinding, so that target is unaffected by this change. https://doc.rust-lang.org/rustc/platform-support/wasm32-unknown-unknown.html#unwinding

It was originally set in #207.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
modeling-app	Ready	Preview, Comment	Mar 3, 2026 6:13pm

[codspeed-hq]

Merging this PR will not alter performance

✅ 166 untouched benchmarks
⏩ 93 skipped benchmarks¹

---

_{Comparing jtran/panic-unwind (4042b6a) with main (0e164ec)²}

Footnotes

1. 93 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (092129a) during the generation of this report, so 0e164ec was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩