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.

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

Update Jupyter Version Table #10608

Closed
pandasa123 opened this issue Aug 10, 2023 · 2 comments
Closed

Update Jupyter Version Table #10608

pandasa123 opened this issue Aug 10, 2023 · 2 comments
Labels
type: feature request New feature or request

Comments

@pandasa123
Copy link

pandasa123 commented Aug 10, 2023

Background

Today, the Jupyter Version Table includes the following information:

Screenshot 2023-08-10 at 2 36 38 PM

Discussion

There are several items I wanted to open for discussion:

  1. What packages should be there? I believe we should be adding qiskit-ibm-runtime to this table as it's a package in the "main" tier (and other packages that are in this tier)
  2. What packages should be removed? For example, there are several "community" items here that we shouldn't have here?
  3. Is it possible to add a toggle for System Information? There are several places where this Version Table is shown. In most cases, the package versions and the Python version are the only things that are essential to show

Next Best Alternative

Our enablement (tutorials / courses), can call get_version_info() directly:

import qiskit_ibm_runtime

qiskit_ibm_runtime.version.get_version_info()

import qiskit

qiskit.version.get_version_info()

!python --version

While this is fine in general, I think the table magic allows us to be consistent easier

CC: @jyu00, @1ucian0, @javabster, @abbycross

@pandasa123 pandasa123 added the type: feature request New feature or request label Aug 10, 2023
@mtreinish
Copy link
Member

mtreinish commented Aug 10, 2023

This was updated in #10242 as part of 0.25.0. In the current release it will show any package currently imported that starts with qiskit that is imported along with the qiskit package version. TBH, I was personally not a fan of keeping the jupyter magic in qiskit, as I think it's utility is very small and it's only because of it's current use in qiskit-tutorials that I think we kept it. What you're doing in "Next Best Alternative" is what I normally recommend people do (or just call qiskit.__version__ and qiskit_ibm_runtime.__version__) if they want to get the versions of the packages of interest. You can easily build a local magic for custom and consistent formatting, all it's basically doing is just building an html table based on the __version__ attributes anyway.

@pandasa123
Copy link
Author

Sounds good! I agree with your thoughts on the Jupyter Magic's place in qiskit

Will close this issue today, and have the NBA as the promoted route instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants