Skip to content
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

Add dwave.cloud.hybrid.Client #378

Closed
randomir opened this issue Apr 6, 2020 · 1 comment
Closed

Add dwave.cloud.hybrid.Client #378

randomir opened this issue Apr 6, 2020 · 1 comment

Comments

@randomir
Copy link
Member

randomir commented Apr 6, 2020

Extending the pool of clients {base, qpu, sw} with the hybrid one.

Solver filtering criterion: category == "hybrid".

In support of dwavesystems/dwave-system#288.

@randomir randomir changed the title Add hybrid client Add dwave.cloud.hybrid.Client Apr 6, 2020
@randomir
Copy link
Member Author

randomir commented Apr 9, 2020

Closed in #379.

@randomir randomir closed this as completed Apr 9, 2020
randomir added a commit that referenced this issue Jul 8, 2020
Changes from 0.7.2:

New Features
---

- Hybrid solvers support (#378):
  - `dwave.cloud.hybrid.Client` is a new client type specialized
    for SAPI hybrid solvers
  - `Solver.hybrid` is a new derived property, also available for
    feature-based solver filtering
- Client certificate SAPI authentication supported via `client_cert`
  and `client_cert_key` config/kwarg parameters (#382)
- `dwave install` now supports `--upgrade` option to (re)install
  partially installed contrib packages, or upgrade stale
  requirements (#381)

Fixes
---

- `qpu`/`sw`/`hybrid` derived solver properties refactored to use
  the new SAPI solver property, `category`
- Nested exception properly propagated by `Future.exception()`
- `dwave install` now enforces the full requirement specifier for
  each contrib dependency
- User home and environment variables are now expanded in
  config file path (#318)

Changes
---

- `Solver.is_*` properties scheduled for removal in 0.8.0
- `Future.error` deprecated in favor of `Future.exception()` and
  scheduled for removal in 0.9.0
- Removed most of Python 2 constructs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant