Since 0.12, Qiskit-Aer notices deprecation warnings to use of PulseSimulato. Because 0.13 will be released after +3 months since 0.12 was released, Qiskit-Aer will stop supports of pulse simulation.
* first pass at removing pulse simulator
* autoformat with black
* remove ref to aer pulse in docs
* fix lint issues
* remove pulse rst
* remove pulse tests
* add release note
* remove open pulse from CMakeLists.txt
* remove pulse tests
* remove remaining pulse codes
---------
Co-authored-by: AngeloDanducci <angelo.danducci.ii@ibm.com>
* add black and clang-format
* apply black and clang-format
* manually format codes that were not covered in black and clang-format
* add targets of clang-format and clean up tox.ini
* apply black with new configuration
* Update CONTRIBUTING.md
Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
* Update .github/workflows/tests.yml
Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
* reformat qiskit_aer, test, tools, and setup.py with length 100
---------
Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Previously the root of the qiskit_aer we were exporing certain modules
and objects using relative imports to do this. However, the qiskit
package sets up a metaimporter to redirect imports from
qiskit.providers.aer to qiskit_aer (for backwards compatibility with the
old aer name) the source package for these relative imports can get
confused on subsequent imports if something also uses the legacy name
(which qiskit itself does on it's optional imports to aer, so that it
supports >1 version). While all the code functions correctly in this
case Python emits a warning saying the package __spec__ doesn't match
anymore. The simplest way to address these warnings is to use an
absoulte import with the package name in it so there is no ambiguity in
the source package on imports.
This commit makes that change to the root of the pacakge which fixes the
warnings. The only thing I'm not sure of is if any other relative
imports elsewhere in the qiskit_aer package will have the same problem
or if this is fixed by just updating the root package. We might need to
do further testing to check.
Fixes#1692
* Deprecate Python 3.7 support in Qiskit Aer
This commit deprecates Python 3.7 support. During the deprecation window
we will continue to fully support Python 3.7 and test it in CI, but it will
emit a warning that we will be removing support for 3.7 in the future to
inform users to upgrade to Python 3.8 or newer. The removal will occur
during a future release at some point over the summer as the upstream
Python EoL date is in June 2023. [1]
[1] https://devguide.python.org/versions/
* Fix lint
* Move comment before if block
Add a new class AerStatevector that supports q.i.s.Statevector interface.
This class uses an internal class AerState that directly access to Aer's
native runtime.
Namespace packages are constant source of problems for users. The python
packaging ecosystem around splitting packages across namespaces is
fragile at the best of times and can often leave a you with an
environment that isn't recoverable (especially when mixing install
methods). There is also a performance hit whenever there is a piece of
the namespace we allow external packages to extend since it requires
doing a full python path search which can be slow depending on the
backing I/O and the number of paths in sys.path for an environment. This
commit addresses the piece from the aer perspective by moving
qiskit.providers.aer to it's own package and namespace 'qiskit_aer'.
Co-authored-by: Hiroshi Horii <horii@jp.ibm.com>
Jun Doi