-
Notifications
You must be signed in to change notification settings - Fork 38
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
Home-Based Config Paths #318
Labels
Comments
Isn't You can double check with:
|
Let me clarify. In this library the call |
Oh, that is a bug. Will fix. Thanks! |
randomir
added a commit
to randomir/dwave-cloud-client
that referenced
this issue
Jun 19, 2020
randomir
added a commit
to randomir/dwave-cloud-client
that referenced
this issue
Jun 19, 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
It seems that at least on OS X the config file paths cannot include home-based paths. For example,
~/foo/my.conf
or$HOME/foo/my.conf
. If it is easy to support these it would provide some added convenience.The text was updated successfully, but these errors were encountered: