Version 0.5.0+ no longer displays output after widget interaction
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter-notebook
- Domain
- frontend
Research direction
Compare ipympl 0.5.0 with a pre-0.5.0 version in a classic Jupyter Notebook, reproducing interaction with an ipympl graph, print(), and ipywidgets.FloatText(). Trace how widget output is displayed after interaction; done means printed text and instantiated widgets appear in the cell output area again or the supported replacement is documented.
Written by the indexing model from the issue text.
Description
I have not labeled this as a "bug report" as I am not sure whether this is a new feature or regression.
I am developing a package for the processing of NMR spectra that makes extensive use of the ipympl backend:
https://github.com/NMRPy/nmrpy
As part of this there are a number of widgets (interactive matplotlib graphs) for phasing and peak picking of the NMR spectra. Some of these widgets print output to the cell output area (below the ipympl widget) after user interaction, using simple print() function calls in the code. In some cases further user input is required for which I have made use of an ipywidgets.FloatText() which is then also displayed in the output area.
As of version 0.5.0 this cell output area is no longer displayed. The widget interaction with the ipympl graphs still works but the text output from print() calls and the ipywidgets output are not there.
- Is this intentional or a regression?
- If intentional, is there a way to get the output area back, or an alternative where to direct text output after interaction with a graph (or instantiate an
ipywidgetswidget) so that it is displayed to the user?
This functionality is crucial to my application and currently I am thus stuck with using ipympl<0.5.0. BTW this is using notebook, not jupyterlab.
- Dominant language
- Jupyter Notebook
- Stars
- 1.7k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from matplotlib/ipympl
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matplotlib/ipympl#623 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matplotlib/ipympl#622 · 13 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
matplotlib/ipympl#612 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
matplotlib/ipympl#611 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
matplotlib/ipympl#609 · 7 comments ·
All issues in matplotlib/ipympl
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cancervariants/metakb#902 ·
-
Two open-case totals on one screen: the Programs tile says 15,858 and the nav badge says 15,868 Openbug frontend maui-pilot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Save States Menu Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100