-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Resolves #262: add qiskit.backend methods... for getting parameter, calibration, and status. * linting quantumprogram * Update _backendutils.py * Update _backendutils.py * Update _basebackend.py * Update _qeremote.py * Update _basebackend.py * Update _quantumprogram.py * Update _qeremote.py * Warning, updates to test, and backencs 1. Added to the quantum program warnings — may of done this incorrect 2. Removed old versions 3. In the configuration we lost the rewrite of the mapping. I agree we want to update the API but first we need the backend configuration to work 4. Made the test use quantum program Still to be done — check why failing some test — add some test to backend that test the test_basebackends that test new methods * Fixing some spelling and linting * Spelling fixes * Lint and spelling * Linter fixes and some spelling in backendutils * Cleaning up the coupling_map @ewinston we decided that all new code should use the new map and all old code the older one. I have remove the complicated identity map we inserted :-) * Renaming configuration as config to fix scope error * Linting in test * Linting more * Fixing the vqe * More linting * Update test_quantumprogram.py * lint errors I found trying to debug the error * Removing backend from quantum_program test * Making the backend object based * Adding tests for the backend object * Linting tests * Spelling and linting * Removing some set_api that are not needed * set log level to debug * Removing the api from the tests and needed by the program * Cleaning up and adding a discover * correct travis.yml env variable specification * Removing more old code * Updated lengths with rename of q_name and c_name * Lint errors found from travis fixed * Moving import order to help travis linter * Revise DeprecationWarnings, add note to docstrings Add a context manager for ensuring the DeprecationWarnings are shown regardless of the user configuration, as by default they are hidden for end users (ie. when not on an interpreter). Revise the strings for the warnings and add entries to the docstrings for visually showing them on the online docs. * Enable deprecation warnings during __init__ Enable the display of deprecation warnings during qiskit.__init__ instead of via a context manager, for simplifying the deprecated calls and help providing visual aids for the editors. * fix cyclic import and scope of configuration These were pylint warnings. The configuration one was due to having a function of of the same name as a parameter in _backendutils.py. * fix linter * remove converting coupling_map to dict * minor lint fix * Small fix to the backends. * Fix LookupErrors, style, comments Fix several backendutils methods raising ConnectionError instead of LookupError when the entities were not found. Update the structure of those methods for simplicity and consistency. Fix commented out code on tests.
- Loading branch information
1 parent
27fd0b3
commit cc2546b
Showing
12 changed files
with
752 additions
and
344 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.