-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken CI #210
Fix broken CI #210
Conversation
bind_parameters()
call for assign_parameters()
bind_parameters()
call for assign_parameters()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for fixing this
@@ -1,6 +1,6 @@ | |||
qiskit-aer>=0.13 | |||
pytest | |||
pylint==2.16.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I worry this might be too loose for pylint which notoriously has had issues with rule stability between even on bugfix releases. But lets give it a try and we can do an exact version pin if needed
CI was broken for four reasons:
pylint
was pinned to version 2.16.2 which doesn't support Python 3.12 and 3.11 officiallyimp
library in favor ofimportlib
and we were using a version ofipykernal
that was importing the old library. The PR pinsipykernal
to the first version supportingimportlib
. See this issue.bind_parameters
forassign_parameters
as explained in the qiskit 1.0 release notes.qiskit.execute
function is not available in Qiskit 1.0 anymore -> Migration guide