Closed eendebakpt closed 2 months ago
hmm... std copy raises this warning. Maybe @jakelishman knows what's going on.
All of these warnings have their stack levels set correctly so that they do not blame user code. Setting the warnings to "show all warnings despite the filters" does show additional warnings, but there is some degree to which this is expected when deprecated functionality is in the process of being removed.
Fwiw, the actual deprecated functionality coming from the Result
object that Aer is producing - the trouble is that Aer is still putting various deprecated Qobj things in its Result
object, which are then dutifully deepcopy
ed. Qiskit isn't actually using deprecated functionality, the problem is just that it's deepcopying some deprecated objects that Aer actually created.
This indeed seems like an issue with qiskit-aer using deprecated functionality. I created https://github.com/Qiskit/qiskit-aer/issues/2233 and will close this issue.
Environment
What is happening?
The qiskit
marginal_counts
method uses deprecated functionality when aResult
object is used as input.How can we reproduce the issue?
What should happen?
No warnings should be generated, but instead the output is
Any suggestions?
No response