Jupyter Blog - Rosio Reyes

Jupyter Community Call: February 2026

2026-02-16T13:26:00+00:00

February 2026 Jupyter Community Call

Hey Jovyans, we’d love for you to join us on our final community call of the year! We want to learn all about the great things you’re doing with Jupyter. The Community Building working group is holding an open call with the community, for people to discuss and share their work. Think of it as a “virtual JupyterCon”: It’s a place to announce and share new things happening in the Jupyter ecosystem.

We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it.

Anyone can attend, for free! Anyone can present; add yourself to the HackMD agenda. Anyone can sit in on the call. Presenters will lead a demo and may leave time to answer questions. Topics should be targeted to broad and global audience. Keep things simple and remember not every listener will be a software engineer.

Event details:

February 25, 2026, at 9:00 AM PDT (15:00 UTC; your timezone)

Agenda (add yourself!) on HackMD
Meeting channel: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Meeting ID: 95228013874 / Meeting Passcode: 659973
Or connect via phone:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592
or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free)
International numbers: https://zoom.us/u/alwnPIaVT

Watch previous calls in our YouTube playlist.

Hey Jovyans, we’d love for you to join us on our final community call of the year!

2025-11-13T16:18:00+00:00

December 2025 Community Call

We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it.

Event details:

December 04, 2025, at 8:00 AM PDT (16:00 UTC; your timezone)

Agenda (add yourself!) on HackMD
Meeting channel: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Meeting ID: 95228013874 / Meeting Passcode: 659973
Or connect via phone:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592
or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free)
International numbers: https://zoom.us/u/alwnPIaVT

Watch previous calls in our YouTube playlist.

Jupyter Community Call: September 2025

2025-07-31T15:11:00+00:00

September 2025 Community Call

Hey Jovyans, we want to learn about the great things you’re doing with Jupyter! The Community Building working group is holding an open call with the community for people to discuss and share their work. Think of it as a “virtual JupyterCon”: It’s a place to announce and share new things happening in the Jupyter ecosystem.

We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it.

Event details:

September 04, 2025, at 8:00 AM PDT (15:00 UTC; your timezone)

Agenda (add yourself!) on HackMD
Meeting channel: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Meeting ID: 95228013874 / Meeting Passcode: 659973
Or connect via phone:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592
or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free)
International numbers: https://zoom.us/u/alwnPIaVT

Watch previous calls in our YouTube playlist.

Jupyter Community Call: June 2025

2025-05-22T15:06:00+00:00

June 2025 Community Call

Hey Jovyans, we want to learn about the great things you’re doing with Jupyter! The Diversity, Equity, and Inclusion (DEI) standing committee is holding an open call with the community for people to discuss and share their work. Think of it as a “virtual JupyterCon”: It’s a place to announce and share new things happening in the Jupyter ecosystem.

We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it.

Event details:

June 11, 2025, at 9:00 AM PST (17:00 UTC; your timezone)

Agenda (add yourself!) on HackMD
Meeting channel: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Meeting ID: 95228013874 / Meeting Passcode: 659973
Or connect via phone:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592
or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free)
International numbers: https://zoom.us/u/alwnPIaVT

Watch previous calls in our YouTube playlist.

Jupyter Community Call: February 2025

2025-01-30T22:59:00+00:00

Hey Jovyans, we want to see the great things you’re doing with Jupyter! The Diversity, Equity, and Inclusion (DEI) standing committee is holding an open call with the community for people to discuss and share their work. Think of it as a “virtual JupyterCon”: It’s a place to announce and share new things happening in the Jupyter ecosystem.

We encourage brief (5 minutes or less) presentations with a demo or screen share, as needed. If you have a GitHub repo or demo web site, please remember to share it.

Anyone can attend, for free! Anyone can present; add yourself to the agenda above. Anyone can sit in on the call. Presenters will lead a demo and spend a few minutes answering questions. Topics should be targeted at a broad Jupyter audience, not just programmers.

Event details:

February 19, 2025, at 9:00 AM PST (17:00 UTC; your timezone)

Agenda (add yourself) on HackMD
Meeting channel: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Meeting ID: 95228013874 / Meeting Passcode: 659973
Or connect via phone:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592
or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free)
International numbers: https://zoom.us/u/alwnPIaVT

Watch previous calls in our YouTube playlist.

JupyterLab 4.2 and Notebook 7.2 are available!

2024-05-22T21:00:00+00:00

JupyterLab 4.2.0 has been released! This new minor release of JupyterLab includes 3 new features, 20 enhancements, 33 bug fixes and 29 maintenance tasks. There were 39 contributors to this release including 10 new contributors to JupyterLab.

Jupyter Notebook 7.2.0 has also been released, including many of the fixes and enhancements in this JupyterLab 4.2.0 release. While the releases on Github provide additional detail on the updates made to both JupyterLab 4.2 and Notebook 7.2, this article highlights some particularly notable changes.

Extension authors can refer to the Extension Migration Guide for information on API updates and details regarding changes to core packages.

Easier Workspaces Management with GUI

It is now possible to manage workspaces from within JupyterLab with the workspaces graphical user interface. This long awaited feature offers users an additional way to interact with workspaces beyond the existing URL and CLI-based options, providing a more user-friendly and accessible alternative for some.

JupyterLab 4.2.0 Workspaces UI

Recently opened/closed files

Jupyterlab-recents, an extension for tracking recent files and directories has now been integrated into core JupyterLab. This extension adds a main menu entry for recently opened/closed files. JupyterLab users now have this native functionality that provides a quick reference to files they have recently worked with. Further development work in JupyterLab core now also allows users to search for and access recently closed files and folders through a modal via the shortcut Ctrl + Alt + A.

JupyterLab 4.2.0 Recently Closed Submodal

Full notebook windowing mode by default

The previously available full notebook windowing mode has now been made the default mode. This mode renders only the cells visible in the window, leading to improved performance. With this mode using the JupyterLab search function is recommended due to false negatives with the web browser’s native search functionality.

Improved Shortcuts Editor

Users can enjoy an improved experience when customizing shortcuts. Various improvements have been made to the shortcuts editor, namely: default shortcuts can be deleted, and shortcuts are sorted appropriately when using a language pack. Entries for shortcuts with varying arguments are also now accurately presented as separate items.

Modal option to delete shortcut key binding.

Dark High Contrast Theme

The JupyterLab Dark High Contrast Theme is now available for users who might benefit from higher contrast as outlined by the WCAG AAA accessibility standards for color contrast.

JupyterLab 4.2.0 Dark High Contrast Theme

Keyboard Shortcuts

The shortcuts extension received some improvements based on user feedback. The Ctrl + D shortcut has been restored to allow users to use to delete a line. In the interest of code editor compatibility the Ctrl + Shift + K shortcut can still be used for deleting lines and multi-cursor selection is now available via the default shortcut: Ctrl + Shift + D. Users are now able to toggle line comments with the shortcut Ctrl + / and toggle block comments with Alt + A, both of which are customizable via the Settings Editor. This release also addresses issues related to using various keys on international keyboards in macOS.

Acknowledgements

Thank you to all the new contributors, we hope to see you back!

JupyterLab: @linlol, @erkin98, @mdietz94, @UntitledError-09, @Susilkessav, @Tanmay-Deshmukh, @AnastasiaSliusar, @milinm, @Rob-P-Smith, @NexVeridian.
Notebook: @afeld

And thank you to returning contributors for their continued work!

JupyterLab: @davidbrochart, @fcollonval, @FoSuCloud, @JasonWeill, @jtpio, @krassowski, @Alanhou1222, @divyansshhh, @itsmevichu, @kolibril13, @sawickid, @andrii-i, @bollwyvl, @brichet, @Mehak261124, @e218736, @echarles, @gabalafou, @m158261, @afshin, @minrk, @RRosio, @trungleduc, @blink1073, @diyoyo, @AllanChain, @ericsnekbytes, @HaudinFlorence
Notebook: @jtpio, @krassowski

Thank you to all the people who tested and provided feedback for the pre-releases! Lastly, thank you to the weekly triage group for triaging JupyterLab, Notebook and JupyterLab Desktop issues: @JasonWeill, @krassowski, @RRosio among others who attend.

Contributors to this blog post: @krassowski, @jtpio, @JasonWeill, @RRosio.

Jupyter Notebook 6.5.0 Release Candidate

2022-09-15T15:01:00+00:00

We’d like to announce the Notebook 6.5.0 release candidate which is available on PyPI.

Notebook 6.5.0rc0 on PyPI

Notebook 6 vs Notebook 7

Jupyter Notebook is a longstanding project that has been loved by many for years. Even with the 2018 release of JupyterLab, a feature-full user interface with a more modern codebase, many people have continued to use Jupyter Notebook. In an effort to continue providing updates to the UI that people know and love, many developers have been working on Jupyter Notebook 7. This transition was outlined in the Jupyter Enhancement Proposal or JEP 79, which highlights the motivation behind an updated codebase and the plans that are currently being carried out. Notebook 7 uses components from JupyterLab and the Jupyter Server package as does JupyterLab, and the UI provides an experience much like the classic user interface that Jupyter Notebook users are familiar with. There are various new features which will be readily available, and improvements are to be made in Jupyter Notebook 7.

Due to this upcoming release, there were some necessary changes that had to be made to Jupyter Notebook 6. Jupyter Notebook 6 has lived in the jupyter/notebook repository whose main branch reflects Notebook 7. Notebook 6 uses the same Python Tornado server architecture, and the NotebookApp class that has been present all through previous Notebook releases. However, as of Notebook 6.5 the static HTML/CSS/JS assets that constitute the user interface have been moved to a different repository, the jupyter/nbclassic repository. Notebook 6.5 aims to be end of life in a reasonable timeframe. With this in mind, Notebook 6.5 will focus on security and bug fixes rather than new features.

NbClassic

With the more sustainable Notebook 7 in the horizon, and Notebook 6.5 being EOL, the NbClassic project is the repository through which enhancements and new features can be offered. NbClassic is a forked version of the 6.5.x branch of Notebook, refactored as a Jupyter Server extension. Through this, users can benefit from the updates to other parts of the ecosystem such as Jupyter Server. While the classic user interface will be available through both Notebook 6 and NbClassic, immediate updates to the classic Notebook UI will be provided through NbClassic.

Since as of Notebook 6.5, the static assets for the UI have been removed from the Notebook repository and are made available to Notebook 6.5 through NbClassic, and the NbClassic repository is also where issues with the classic user interface should be reported. The NbClassic project aims to provide intermediary support to those users of Notebook 6 who for various reasons may not yet be able to upgrade to Notebook 7. As NbClassic can be seen as a drop-in replacement to Notebook 6, its support and lifecycle will follow the one defined for the Notebook 6 product line. For more details on the maintenance of Notebook projects please have a look at the Maintained versions section in the readme.

As from version 0.4.0, NbClassic is a Jupyter Server extension that is backwards compatible with most extensions built for Notebook for version 6. If your extension does not work on NbClassic, we invite you to open an issue on the NbClassic GitHub repository so we can help you resolve it.

Some Use Cases

One reason a user might not be able to update may be due to a user toolset that incorporates an extension that has not yet been ported to Notebook 7 and JupyterLab. In these cases, it will be important for extension developers to place an upper bound in their Notebook dependencies so that only versions below Notebook 7 will be installed. There may also be users who have both JupyterLab extensions and Notebook extensions as a part of their toolset.

Another scenario may include DevOps Engineers who may provide Notebook 6 or 7, NbClassic, and JupyterLab to users to account for the different needs of many teams. In that scenario, the user can choose his user interface that runs on the same server port. For example if both Notebook 7 and NbClassic are installed, the default interface will be Notebook 7 under /tree URL while the NbClassic interface will be available under nbclassic/tree URL

Compatibility

For the various use cases, we aim to foster the coexistence of these projects while users and developers begin adapting to Notebook 7. Jupyter Notebook 7, JupyterLab and NbClassic share the same server architecture, allowing users to more feasibly use them interchangeably. On the other hand, Jupyter Notebook 6 will only be tied to NbClassic for the static assets that it will use. Extensions that work with Notebook 6 will be compatible with NbClassic while extensions developed for JupyterLab will work with Notebook 7. If users wish to use the upcoming Notebook 7 but have the ability to occasionally work with extensions that have not been ported, NbClassic will provide this. You can use NbClassic with the CLI command jupyter nbclassic .

DevOps Engineers will have to use a slightly different command to enable the notebook extension on NbClassic. For example, they will have to use jupyter nbclassic-extension instead of jupyter nbextension. We are working on updating the documentation to reflect those changes.

Next Steps

With the release of Jupyter Notebook 6.5.0rc0, we hope to reach those who continue to use Notebook 6 and hear about your experience. The Jupyter Notebook 6.5.0 release candidate can be installed with pip: pip install notebook==6.5.0rc0. For those who wish to continue using a user interface much like the classic Notebook that is familiar, Notebook 7 has an alpha release and will provide a well supported and evolving user interface. Alongside working to release Notebook 6.5 and the upcoming Notebook 7 release, we will be continuing to work on preparing NbClassic to be used with the various other Jupyter projects and gearing up for the first major release.

We would be happy to hear about your experience using Notebook 6.5.0rc0. For any questions, feedback, or bug reports, we invite you to open an issue in the NbClassic repository.

Sincerely,

Project Jupyter

About the Author
Rosio Reyes is a Software Engineer at Anaconda working as a part of the OSS Jupyter team. She is a Jupyter Notebook Steering Council Member and contributes to the Notebook and NbClassic projects.

Thank You to Contributors to this blog
Eric Charles is a Software Engineer at Anaconda, Datalayer and Quansight working as a Tech Lead on the OSS Jupyter team. He is a Jupyter contributor and a member of the Jupyter Notebook Steering Council. He contributes to many Jupyter Projects and provided an outline for the blog as well as many edits and additions.

Eric Gentry, a Software Engineer at Anaconda working on the OSS Jupyter team. He is a Jupyter Notebook Steering Council Member and contributes to the Notebook and NbClassic projects. He also provided many edits for the blog.

Special thanks to the Jupyter Notebook Meeting Group for their feedback.