Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore support for the legacy notebook mechanism from 0.16 #7122

Merged
merged 2 commits into from
Aug 9, 2024

Conversation

jleibs
Copy link
Member

@jleibs jleibs commented Aug 8, 2024

What

Some systems are still incompatible with the new anywidget based notebook approach.

Keep the old way of doing things around for the time being. This could probably be improved with new technology we've created, but this is a verbatim copy of how things worked in 0.16.

image

Checklist

  • I have read and agree to Contributor Guide and the Code of Conduct
  • I've included a screenshot or gif (if applicable)
  • I have tested the web demo (if applicable):
  • The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
  • If applicable, add a new check to the release checklist!
  • If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

To run all checks from main, comment on the PR with @rerun-bot full-check.

@jleibs jleibs marked this pull request as ready for review August 8, 2024 19:31
@jleibs jleibs merged commit 0a8dedf into main Aug 9, 2024
35 of 36 checks passed
@jleibs jleibs deleted the jleibs/legacy_notebook branch August 9, 2024 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Restore legacy notebook API
2 participants