Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Implement update_display #10048
sets a display id.
updates the display in-place.
This is implemented through adding the
referenced this pull request
Nov 10, 2016
Here's an example demonstrating this with current master of ipykernel, notebook now that those PRs have been merged.
This is my interpretation of proposals from @fperez and @jasongrout about creating a handle and auto-generating a display_id with a boolean flag (in this case, I used
So the quickest way to create and update a display without needing to generate an id yourself:
handle = display(x, display_id=True) handle.update(y) handle.update(z)
Possible functionality that is currently excluded:
changed the title from
[WIP] Implement update_display
Nov 18, 2016
We can refine/revise the APIs in subsequent PRs, but this one is complete enough for people to play with and build opinions about, I think. Thanks, @rgbkrk!
@willingc , you will also see
It means "end of positional only arguments". Above it means that
We're planning to keep supporting IPython 5 for Python 2 users for some time, but make IPython 6 require Python 3. As this is a new feature in IPython, Min has targeted it for IPython 6. We could maybe make a distinction between user-facing features and infrastructure features, and allow backporting some of the latter. I'd be -0.25 on doing that.
Separately, at some point the applications will require Python 3. Hub already does. For those, we don't plan to make an LTS version with Python 2 support as we have for IPython.
I'm okay targeting this for 5.x as well, if people have that preference. I just wanted to note that my experience was slightly improved by the fact that IPython 6 has dropped py2 support. The differences are small, so it wouldn't be a big deal to backport.
It is only