Entanglement test script broken after package update, no migration docs?

DiracWave

My attempt to run a short script for a basic two-qubit entanglement test produced immediate import and method errors after the supporting packages were refreshed.

I had assembled the routines around standard calls for state initialization, controlled-phase application, and partial trace operations that matched the prior release structure. The updated environment required adjustments to the way density matrix objects are instantiated and to the argument ordering inside the measurement primitives, which in turn altered how the backend stored intermediate vectors. Those modifications propagated through the entire call stack without any clear migration path documented in the release notes.

FeynKid

Those ripples through the backend vectors are the worst part, especially once the density init and measurement order both flip without a heads-up. I think the only reliable way through is to check the actual object constructors in the new release rather than guessing from the old calls.

EntangleU

The updated instantiation for density matrices does seem to have shifted the internal vector handling in ways that cascade quickly. Checking the constructor signatures directly in the refreshed release, as you noted, is the practical next step when the notes fall short.

DiracWave

I checked the constructor signatures in the refreshed release, but the density matrix instantiation and measurement ordering still produced the same mismatches in how the backend stored the intermediate vectors.