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 support for boolean config variables #113

Closed
randomir opened this issue Apr 12, 2018 · 0 comments · Fixed by #427
Closed

Add support for boolean config variables #113

randomir opened this issue Apr 12, 2018 · 0 comments · Fixed by #427
Assignees
Labels

Comments

@randomir
Copy link
Member

Use case: permissive_ssl.

Currently, every non-null value is true.

It would be nice to support: on, off, true, false, 0, 1.

@randomir randomir self-assigned this Apr 13, 2018
randomir added a commit to randomir/dwave-cloud-client that referenced this issue Sep 20, 2020
randomir added a commit that referenced this issue Sep 22, 2020
Changes since 0.7.7:

New Features
---

- `Client` instance defaults via `defaults` constructor argument (#425)
- `Client` class defaults in `Client.DEFAULTS`
- Parsing of boolean options in configuration files. `on`/`off`,
  `true`/`false`, `1`/`0` all work as expected (#113)
- `@deprecated` utility decorator
- `aliasdict` utility `dict` subclass enabling lazy access to alias keys

Fixes
---

- Documentation refactor and update

Changes
---

- Removed legacy config file format (`.dwrc`) support (#138)
- Removed some of the deprecated `Solver.is_*` properties
- Removed support for deprecated formats: `bqm-ref` and `bq-zlib`.
- Removed support for more than first three positional arguments in
  `Client` constructor (`endpoint`, `token` and `solver`). Positional
arguments in the constructor will be deprecated eventually.
- `Client.solvers` scheduled for removal in 0.9.0
- Deprecated `Future.occurrences` in favor of `Future.num_occurrences`
- Deprecated `samples` and `occurrences` keys in
  `Future`/`Future.result()`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant