Dwave-inspector

Latest version: v0.5.2

Safety actively analyzes 702353 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

0.4.2

Bug Fixes

* Use `vcrpy`-compatible version of `urllib3` (`<2`) for testing in https://github.com/dwavesystems/dwave-inspector/pull/157
* Migrate to codecov's orb from the deprecated uploader in https://github.com/dwavesystems/dwave-inspector/pull/158
* Update examples to use newer QPU in https://github.com/dwavesystems/dwave-inspector/pull/155

0.4.1

Upgrade Notes

- The `.show()` call does not return a `RichDisplayURL` anymore. Instead, we reverted to returning URL in a plain `str`. Jupyter viewer will display the inspector inline if possible, otherwise the URL is opened in a browser.

To render the inspector URL inline in a Jupyter notebook cell, independently of the `.show()` call, you can do:

url = dwave.inspector.show(...)
...
from dwave.inspector.utils import RichDisplayURL
RichDisplayURL(url)

Bug Fixes

- Fix duplicated inline render of the Inspector in GUI Jupyter in case when the returned (rich URL) object is displayed in the same cell the `dwave.inspector.show()` was called. See [\152](https://github.com/dwavesystems/dwave-inspector/issues/152)

0.4.0

New Features

- Add support for jupyter-server-proxy. Inspector URL gets rewritten prior to opening/viewing according to external URL as defined by the new config environment variable: `DWAVE_INSPECTOR_JUPYTER_SERVER_PROXY_EXTERNAL_URL`. See [\144](https://github.com/dwavesystems/dwave-inspector/issues/144)

- Add support for Python 3.11

- Add support for dimod~=0.11.0 and dimod~=0.12.0

- Add support for running the inspector behind a network proxy. Now users can register a URL rewriter specific to their environment using the `inspectorapp_proxies` entry point. See [\141](https://github.com/dwavesystems/dwave-inspector/issues/141)

- Use relative API paths to enable app hosting on externally-configured paths (app\110). See [\146](https://github.com/dwavesystems/dwave-inspector/issues/146).

- Render inspector inline in Jupyter notebooks. See [\109](https://github.com/dwavesystems/dwave-inspector/issues/109) and [\#133](https://github.com/dwavesystems/dwave-inspector/issues/133).

Upgrade Notes

- Drop Python 3.6 support

- Drop dimod~=0.8.0 and dimod~=0.9.0 support

- Custom viewer can now return `False` to signal a non-blocking `show()` behavior is desired. Previously the value returned was ignored by the caller.

- Lower bound on Flask version is now 2.2.

Bug Fixes

- Improve error handling and display in `dwave-inspectorapp` (app\100)

- Make `show()` non-blocking regardless of the `block` argument when no viewer manages to open the inspector page. See [\139](https://github.com/dwavesystems/dwave-inspector/issues/139).

- Upgraded JSON serialization to use Flask's new `DefaultJSONProvider` (introduced in Flask 2.2). The "old" way is deprecated by Flask in 2.2, to be dropped in next minor release, 2.3.

0.3.0

New Features

- Add support for Zephyr topology. See [\137](https://github.com/dwavesystems/dwave-inspector/issues/137).

0.2.11

New Features

- Add support for (serialization of) NumPy types used anywhere in the inspector data served from the Inspector web server (Flask app). See [\81](https://github.com/dwavesystems/dwave-inspector/issues/81).

Bug Fixes

- Use of embeddings with NumPy types was not previously possible. Now it is. See [\127](https://github.com/dwavesystems/dwave-inspector/issues/127).

0.2.10

New Features
------------

- Support opening of external visualizer links when running in vscode-based Leap IDE's Simple Browser (`dwave-inspectorapp97`). See 134.

Page 2 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.