Conversation
e387b89 to
1a8c0b9
Compare
0762d7b to
4eda395
Compare
4eda395 to
ae0f337
Compare
|
When you say some envvars have been deprecated, does that mean they will still continue to work (and potentially emit a warning)? |
Cool. We should make a note of this in any migration documentation. |
@notmgsk Definitely. Updating docs is in the epic :) |
|
|
||
| def validate_qubit_list(qubit_list: Sequence[int]) -> Sequence[int]: | ||
| """ | ||
| Check the validity of qubits for the payload. |
There was a problem hiding this comment.
Maybe note what the criteria are
There was a problem hiding this comment.
I should have mentioned: this and the two functions around it were simply moved over from _base _connection.py, so I don't know a ton about their implementation
|
🎉 This PR is included in version 3.0.0-rc.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Authored-by: Andrew Meyer <ameyer@rigetti.com>
Authored-by: Andrew Meyer <ameyer@rigetti.com>
Relates to issue #1298
High-level changes:
PyquilConfigwithQCSClientConfiguration. This deprecated all the old env vars, likeQVM_URLandQUILC_URL, which are now:QCS_SETTINGS_APPLICATIONS_PYQUIL_QVM_URLQCS_SETTINGS_APPLICATIONS_PYQUIL_QUILC_URLapi.Client*QVMCompilerandQPUCompilercode moved into existingAbstractCompilerbaseQVMCompilernow produces aPrograminstead ofPyQuilExecutableResponse. This means thatQVM.load()always takes aPrograminstead of something "compiled" (QVM.requires_executablewas also removed as it is moot)api/_errors.py)api.Clientto be more of a client factory, rather than have it be a do-all client