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.

Sign up for GitHub

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

Jump to bottom

why is qiskit_backend_overview a magic instead of a function/method? #6378

Closed
1ucian0 opened this issue May 9, 2021 · 2 comments
Closed

why is qiskit_backend_overview a magic instead of a function/method? #6378

1ucian0 opened this issue May 9, 2021 · 2 comments
Labels
type: enhancement It's working, but needs polishing

Comments

@1ucian0
Copy link
Member

1ucian0 commented May 9, 2021

Having qiskit_backend_overview as a qiskit.tools.jupyter magic is not ideal. It creates unintuitive situations. For example, from qiskit.tools.jupyter import qiskit_backend_overview does not work. And %qiskit_backend_overview fails if no load_account() was not executed yet.

I suggest to make qiskit_backend_overview a method in the provider or just a standalone function.

Or is there any key advantage in having it as a magic?
@1ucian0 1ucian0 added the type: enhancement It's working, but needs polishing label May 9, 2021
@nonhermitian
Copy link
Contributor

I would just deprecate it and remove. It is legacy code that has been replaced by other tools in the IBM Cloud.

@jakelishman
Copy link
Member

This was removed in #11513.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement It's working, but needs polishing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@1ucian0 @nonhermitian @jakelishman