Closed garrison closed 8 months ago
Specifically, the changed behavior relates to the following line:
Before https://github.com/qiskit-community/qiskit-nature/pull/1248 landed, this line resulted in mo_coeff
being an ndarray
. But now, with the most recent Qiskit Nature main
, it is instead a qiskit_nature.second_q.operators.tensor.Tensor
.
We should also revert #407 as part of the fix to this, when that day comes.
I've added the "urgent" label, because now that https://github.com/Qiskit/qiskit/pull/11086 (removal of qiskit.algorithms
) has been merged to Qiskit, CKT no longer works with Qiskit main
, which is expected to become Qiskit 1.0. The problem is that we are now pinned to qiskit-nature>=0.6.0, < 0.7
, but the latest Qiskit Nature consistent with that constraint still imports -- in various places -- from qiskit.algorithms
and nowhere from qiskit_algorithms
.
One thing we could ask for is a qiskit-nature
0.6.3 release that depends on and imports from qiskit_algorithms
instead of qiskit.algorithms
, so that code relying on Qiskit Nature 0.6.X can continue to work. Another option is to make our code compatible with Qiskit Nature 0.7 (this issue). And, of course, another option is to continue working toward removing the Qiskit Nature dependency altogether (#275). No matter what we choose, it looks like Jan 31 is our deadline if we want to continue being compatible with the latest Qiskit release (and we have much less time if we want to be compatible with Qiskit 1.0.0pre1).
I haven't figured out exactly why yet, but the merging of https://github.com/qiskit-community/qiskit-nature/pull/1248 broke our "development version tests."