internal: No std broken on main

[Person-93]

The main branch currently has failing no_std jobs. See #6376

[codspeed-hq]

Merging this PR will degrade performance by 11.56%

⚠️ 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 regressed benchmarks
✅ 139 untouched benchmarks
⏩ 6 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	into_biguint_zero	1.2 µs	1.4 µs	-11.89%
❌	critical_section_creation	1.3 µs	1.5 µs	-11.24%

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:no_std_broken_on_main (21f0932) with main (ee629fb)}

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]

@davidhewitt , I am not sure why zope installation is failing or why that's on no_std, but can you merge this PR anyway and have that be a separate PR? This one has other fixes.

[davidhewitt]

The zope install is non-blocking, the real failure is

pytests/.nox/test/lib/python3.14/site-packages/pyo3_pytests/pyo3_pytests.cpython-314-x86_64-linux-gnu.so' has no attribute 'path' (most likely due to a circular import)

Which looks likely to be related to gating that module on std?

[Person-93]

The zope install is non-blocking, the real failure is

pytests/.nox/test/lib/python3.14/site-packages/pyo3_pytests/pyo3_pytests.cpython-314-x86_64-linux-gnu.so' has no attribute 'path' (most likely due to a circular import)

Which looks likely to be related to gating that module on std?

Can you merge this PR and open that as a separate issue?