difference in plt.gca() behaviour between inline and notebook backends
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter-notebook, matplotlib
- Domain
- backend, data-visualization
Research direction
Reproduce the report with a notebook cell that creates a 3D axes, followed by a cell using plt.gca(), in both the inline and notebook backends. Compare the current-plot behavior when running through an IPython kernel. Done means both backends consistently handle the current plot across cell boundaries.
Written by the indexing model from the issue text.
Description
I have one notebook cell that creates a 3D axes, which I want to plot into in the next cell.
With the inline backend
we see that the "current plot" has been forgotten, and plt.gca() creates a new 2D plot.
With the notebook backend
The behaviour is different
and plt.gca() remembers the 3D plot across the cell boundaries.
Expected behaviour
The same in both cases, ideally the remembering the current plot across the cell boundary. I'm not sure which behaviour is "correct" but the difference is a problem when I'm running code in an ipython kernel from a client.
- Dominant language
- Jupyter Notebook
- Stars
- 31
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 ipython/matplotlib-inline
-
Support animations Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
ipython/matplotlib-inline#61 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ipython/matplotlib-inline#59 ·
-
Publish changelog Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ipython/matplotlib-inline#57 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ipython/matplotlib-inline#54 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
ipython/matplotlib-inline#44 · 1 comment ·
All issues in ipython/matplotlib-inline
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
punkpeye/mcp-remote#369 ·
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
bug p:3-mid pydanty:bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pydantic/pydantic-ai#8643 · 1 comment ·