Skip to content
This repository was archived by the owner on Aug 19, 2023. It is now read-only.

Conversation

mtreinish
Copy link
Member

Summary

This commit adds details to the install guide and the install from
source guide on new warnings being emitted by terra in the 0.9 release.
Added in Qiskit/qiskit#2842 when qiskit-aer or
qiskit-ibmq-provider can not be found by terra on initial import it will
emit a warning to inform the user of that state. This is done because
today the user will have no idea if they forgot to install these
components (or more likely python packaging screwed up the installation)
and aer or ibmq can't be found. They will then try to use either
qiskit.Aer or qiskit.IBMQ only to be met by a confusing ImportError.
This is a very common occurrence for users and causes a great deal of
confusion. However, since emitting a warning on import is potentially
undesirable behavior for any users that only use qiskit-terra by
itself. If they never have any intent of importing qiskit.Aer or
qiskit.IBMQ then emitting a warning is fairly annoying. This commit
documents these warnings and more importantly how to suppress them for
these users, so that they do not have to be concerned about seeing the
warnings in perpetuity moving forward if they do not want to.

This updates both the install guide and the contributing guide since
it's conceivable a user would refer to either guide when installing
terra as a standalone component.

At the same time a stale reference to a warning that as of #304 merging
no longer will be emitted when installing the qiskit metapackage is
removed from the install documentation.

Details and comments

This commit adds details to the install guide and the install from
source guide on new warnings being emitted by terra in the 0.9 release.
Added in Qiskit/qiskit#2842 when qiskit-aer or
qiskit-ibmq-provider can not be found by terra on initial import it will
emit a warning to inform the user of that state. This is done because
today the user will have no idea if they forgot to install these
components (or more likely python packaging screwed up the installation)
and aer or ibmq can't be found. They will then try to use either
qiskit.Aer or qiskit.IBMQ only to be met by a confusing ImportError.
This is a very common occurrence for users and causes a great deal of
confusion. However, since emitting a warning on import is potentially
undesirable behavior for any users that only use qiskit-terra by
itself. If they never have any intent of importing qiskit.Aer or
qiskit.IBMQ then emitting a warning is fairly annoying. This commit
documents these warnings and more importantly how to suppress them for
these users, so that they do not have to be concerned about seeing the
warnings in perpetuity moving forward if they do not want to.

This updates both the install guide and the contributing guide since
it's conceivable a user would refer to either guide when installing
terra as a standalone component.

At the same time a stale reference to a warning that as of Qiskit#304 merging
no longer will be emitted when installing the qiskit metapackage is
removed from the install documentation.
@mtreinish
Copy link
Member Author

This is also set to be included in the terra release notes here: Qiskit/qiskit@b768804 as part of Qiskit/qiskit#2919

@jaygambetta jaygambetta merged commit 2de20c0 into Qiskit:master Aug 14, 2019
@mtreinish mtreinish deleted the terra-standalone-warning-notes branch August 15, 2019 12:20
jakelishman pushed a commit to jakelishman/qiskit-terra that referenced this pull request Aug 11, 2023
…-metapackage#404)

This commit adds details to the install guide and the install from
source guide on new warnings being emitted by terra in the 0.9 release.
Added in Qiskit#2842 when qiskit-aer or
qiskit-ibmq-provider can not be found by terra on initial import it will
emit a warning to inform the user of that state. This is done because
today the user will have no idea if they forgot to install these
components (or more likely python packaging screwed up the installation)
and aer or ibmq can't be found. They will then try to use either
qiskit.Aer or qiskit.IBMQ only to be met by a confusing ImportError.
This is a very common occurrence for users and causes a great deal of
confusion. However, since emitting a warning on import is potentially
undesirable behavior for any users that only use qiskit-terra by
itself. If they never have any intent of importing qiskit.Aer or
qiskit.IBMQ then emitting a warning is fairly annoying. This commit
documents these warnings and more importantly how to suppress them for
these users, so that they do not have to be concerned about seeing the
warnings in perpetuity moving forward if they do not want to.

This updates both the install guide and the contributing guide since
it's conceivable a user would refer to either guide when installing
terra as a standalone component.

At the same time a stale reference to a warning that as of Qiskit/qiskit-metapackage#304 merging
no longer will be emitted when installing the qiskit metapackage is
removed from the install documentation.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants