Rust API for pyinitconfig

[Person-93]

Adds a rust API to initialize the embedded interpreter with configuration.

Closes #6153

[ngoldbaum]

According to codecov almost none of the API surface is tested. Can you please make sure there's coverage for all the InitConfig methods you're proposing to add?

[codspeed-hq]

Merging this PR will degrade performance by 0.43%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 2 regressed benchmarks
✅ 137 untouched benchmarks
⏩ 6 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	into_u128_small	876.1 ns	1,041.4 ns	-15.87%
❌	into_u128_zero	816 ns	925.7 ns	-11.85%
⚡	into_biguint_small	1.5 µs	1.3 µs	+16.79%
⚡	into_biguint_zero	1.4 µs	1.2 µs	+13.49%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing Person-93:pyinitconfig (5a5770e) with main (6a930e9)}

Footnotes

1. 6 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. ↩

[Person-93]

@codspeedbot fix this regression

[Person-93]

Maintainers (@ngoldbaum), is test coverage OK. Do we need a test case which deliberately causes initialization to fail so the error handling code is covered?

[davidhewitt]

Thanks, some various thoughts and suggestions. Sorry it took a long time to get around to this one.

[davidhewitt]

Thanks, this looks good to me!

[Person-93]

I'm ignoring the test_init_fail testcase for now.

[Person-93]

@ngoldbaum what happened to CI for this PR? I see that you cancelled them after they were stuck for a few hours, so what happens now?

[ngoldbaum]

Maybe try debugging locally or in your fork? I canceled CI because it was blocking CI on other PRs.

[Person-93]

@ngoldbaum , I tried running CI again to see if it was a transient issue or if I could get logs, and I've confirmed that the pytest test_comparisons.py is what hangs. Please cancel CI again; sorry for the trouble.

[ngoldbaum]

I usually enable actions in my fork of a project when I’m limited by permissions like you’re hitting here.