You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several items I wanted to open for discussion:
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)
What packages should be removed? For example, there are several "community" items here that we shouldn't have here?
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:
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.
Background
Today, the Jupyter Version Table includes the following information:
Discussion
There are several items I wanted to open for discussion:
Next Best Alternative
Our enablement (tutorials / courses), can call
get_version_info()
directly:While this is fine in general, I think the table magic allows us to be consistent easier
CC: @jyu00, @1ucian0, @javabster, @abbycross
The text was updated successfully, but these errors were encountered: