Jupyter notebooks and visualizations should be moved to a different package
See original GitHub issueIn the quest for lighting Terra, it seems to me that there is some consensus for moving notebooks [1, 2] (and the associated visualization tools [3]) to a different repo/package, since they effectively are a layer on top of Terra.
The task associated with this are:
- Confirm the consensus
- Choose a name a create the repo/package
- Move code, tests, and issues for:
- Non-text visualizations associated with notebooks (circuit, city plots, etc)
- Jupyter tools in
qiskit/tools/jupyter
This will allow us to move towards a totally network-independent Terra, to reduce the noise associated with issues and PRs on the jupyter layer, and to light dependencies.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Jupyter Notebooks: Avoid Making These 4 Mistakes
Jupyter notebooks allow us to combine code, narrative text, equations, and visualizations all in a single document. But, with such great ...
Read more >Why Data Scientists Need to Move from Jupyter Notebooks to ...
The issue with such a scenario is that a data scientist using a different version of the same library, such as NumPy, may...
Read more >How to Use Notebooks in Python | LearnPython.com
To open an existing notebook, simply browse the folders and click on the file with the .ipynb extension (which corresponds to Jupyter notebooks) ......
Read more >Move your Jupyter notebooks to an Azure DataBricks workspace
The first code change we need is to add a new import and delete another in the first code cell. We don't need...
Read more >Should You Use Jupyter Notebooks in Production? - Neptune.ai
Jupyter Notebooks have been around for quite some time now. They're used a lot in machine learning, mainly for experimentation and visualization.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

For what is worth, I agree with @1ucian0 and believe that moving that layer to another package is a sensible thing and hope it can be reevaluated at some point.
The move would not imply reducing the importance of visualizations, nor incur in changes to the stable interface - as a matter of fact, it would be pretty transparent and straightforward. We already have an example of that transition in the split of the
IBMQProvider, which did contain similar implications (popular feature and stable interface) and was rather uneventful.With the risk of re-hashing older discussions, I think we should also throw into the mix the importance of a lean terra not only for 1.0, but for the present work in other areas. So basically +1 to @1ucian0 !
I dont remember any user complaining about that. It’s mostly about testing time and responsibility separation.