-
Notifications
You must be signed in to change notification settings - Fork 370
Pin Qiskit to <2
in next release
#904
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
Conversation
I am wondering - in the requirements.txt already exists a version limit for qiskit
Would it be better to keep the version restrictions in one place especially since its a direct dependent i.e. |
Pull Request Test Coverage Report for Build 13954831611Details
💛 - Coveralls |
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.
Just a comment to this:
The constraint can be removed when QML achieves full compatibility with Qiskit 2.
Before this it has a constraint >=1.0 so that rather than being removed (depending in what removed is exactly) the upper bound could be removed but that's likely then to become the lower bound i.e. >=2.0 I would think.
* Pin Qiskit to `<2` in next release * Update constraints.txt * Update requirements.txt (cherry picked from commit de2cf2c) # Conflicts: # requirements.txt
* Pin Qiskit to `<2` in next release (#904) * Pin Qiskit to `<2` in next release * Update constraints.txt * Update requirements.txt (cherry picked from commit de2cf2c) # Conflicts: # requirements.txt * Update requirements.txt --------- Co-authored-by: Edoardo Altamura <38359901+edoaltamura@users.noreply.github.com>
Summary
Pinning Qiskit<2 will avoid breaking changes to affect current installations. This potential effect was raised in #897. The constraint can be removed when QML achieves full compatibility with Qiskit 2.