Dear programming hivemind: do not buy @logitechgaming.bsky.social even if that's the only option to get TKL. When their keyboard breaks, the support will baselessly require installing GHub (which they do not support on Linux, and which cannot be installed on corporate OS) in order to verify warranty
Hot off the press: a new JupyterLab extension that brings advanced, interactive visualizations to your JSON, YAML, and CSV files, powered by the jsoncrack library.
➡️ Repo: github.com/jtpio/jupyte...
💡 Try it in the browser: jtpio.github.io/jupyterlab-j...
If you are using AI to open PRs without considering previous reviews and ignoring PR templates, you are not adding value. The point of good first issues was to let humans learn the contribution flow, not for AI to score virtual points.
#JupyterLab 4.6.0a3 enhances the file browser:
- more breadcrumbs are shown to fill space
- name sort order can be changed
- you can 'Open in Terminal' from context menu
Also:
- you can paste code cells without outputs
- before deleting a cell from cell toolbar, you will see a confirmation dialog
#JupyterLab 4.5.5 and 4.6.0a3 are out 🚀
v4.5.5 includes bug fixes for:
- table of contents in Markdown
- theme settings in non-English locales
- comms subshell resource management
- slow selection of lines in editor
- scroll anchoring
A viewer for Parquet, SQLite, and Avro files in JupyterLab.
Check out our new JupyterLab extension: Arbalister. 🏹
Built upon Apache Datafusion, @jupyter.org , and @arrow.apache.org , it lazily fetches rows so that you can view files larger than memory!
blog.jupyter.org/instantly-vi...
JupyterLab 4.5 and Jupyter Notebook 7.5 are here! 🎉
Highlights 🎁
- Enhanced notebook scrolling behavior
- Native audio and video support
- New Terminal search
- Debugger, Notebook and File Browser improvements
Check out the blog post to learn more!
blog.jupyter.org/jupyterlab-4...
Introducing Molview - the ipython/jupyter widget version of nano-protein-viewer🔍:
I used to think the friction in community OSS/corporate dynamics comes from a difference in culture between organizations and teams. The more I see the same team flip between amazing and questionable contribution trajectory the more I think this comes down to changing internal direction/incentives.
It is hard to express criticism as an established maintainer. The words which I could say as a user now hit differently, even if I mean the same thing.
There are two things you should not remove when transitioning to a metapackage: integration tests and documentation. In fact, the transition should double down on these two things as they are critical to ensure the packages integrate well, and that discoverability is preserved.
If you will release a new, better, version but without a feature I like, I might come back and contribute it again.
If you release a new broken version, I may not be able to convince stakeholders to engage and come back, the trust in the project will be lost.
A mismatch of expectation on what irks #OSS maintainers: I saw folks really worry about removing a feature I contributed due to lack of bandwidth to port it to new version - but this was absolutely fine! I saw them remove tests and ignore my warning against it - and this is what in fact made me sad.
I think I tracked it down and Zach contributed this :) Thank you!
I'm really curious what is on the contributions slides. Is this a specific repo/subproject? How was it generated?
To install from PyPI:
pip install --pre --upgrade jupyterlab==4.5.0rc0
You can also install the RC from conda-forge (anaconda.org/conda-forge/...).
Thank you to Rosio Reyes for compiling the release notes, and thank you to everyone who contributed!
New debugger features include a "Paused in Debugger" overlay, better breakpoint and callstack cell annotations, and evaluation in a debugger console.
Search in terminal is now integrated with JupyterLab search widget
Audio and video files can be opened in the main area
New Python file can be created directly from context menu on the file browser.
New exciting features are coming to #JupyterLab 4.5.0. Please test the release candidate before & during the JupyterCon (next week!)
Major enhancements around:
- performance and scroll stability
- notebook editing
- table of contents
- debugger
- terminal
jupyterlab.readthedocs.io/en/latest/ge...
We've learned that our member communities care a *lot* about cloud cost transparency and reliability, so we're working hard to drill down into user data about costs and usage for community leaders to access.
Go from JupyterLab user to creator 🚀
At JupyterCon 2025, learn to build + publish custom extensions for real-world workflows — guided by experts in JupyterLab development.
🗓️ Nov 3 | San Diego
Details: sched.co/28H2m
Register: events.linuxfoundation.org/jupytercon/r...
🚨 The deadline for Jupyter Community Funding Proposals (blog.jupyter.org/your-ideas-o...) has been extended to October 5th, 2025 ( by one week). We've got a few great-looking proposals in the works (github.com/orgs/jupyter...), so you've all got another 7 days to write!
Register for JupyterCon 2025 by October 3 and save $300
WHO’S IN? JupyterCon is coming to San Diego Nov. 4-5 with bonus days for Technical Training (Nov. 3) & Community Sprints (Nov. 6).
Save $100 when you register by Oct. 3.
🔸 View the schedule: bit.ly/4gpqkzy
🔸Register: bit.ly/47C1XMK
A reminder that there are two Call for Proposals out from the Jupyter Foundation!
👉 Jupyter Community Workshops: blog.jupyter.org/jupyter-comm...
👉 Jupyter Community Support funding: blog.jupyter.org/your-ideas-o...
Check them out and share the word!
You’re invited to join the next Jupyter Community Call on September 4th, 2025.
Get updates from across the Jupyter ecosystem, hear talks from community members, and get involved. It’s a great way to connect, contribute, and engage!
The Zoom link in our blog post:
blog.jupyter.org/jupyter-comm...
Jupyter Community Workshops are back! Workshops will be held through February 2026.
The call for proposals is open until September 7th! Learn more and submit your proposal here:
blog.jupyter.org/jupyter-comm...
Have a great idea for Project Jupyter? We want to help you build it! 🚀
The Jupyter Foundation is now accepting funding proposals from all community members. This is your chance to make a direct impact. Learn how to apply! 👇
blog.jupyter.org/your-ideas-o...
👋 JupyterLab and Jupyter Notebook users:
What's one thing you'd love to see improved in JupyterLab, Jupyter Notebook, or JupyterLite?
The team is prepping the upcoming 4.5/7.5 releases and wants to tackle some usability issues.
Drop your feedback below, this will help prioritize what gets fixed!👇
JupyterLab 4.4 and Jupyter Notebook 7.4 will be available very soon.
And they are coming with a couple of nice improvements and bug fixes 🎁
So I just published a new video to do a quick tour of these new features 🎥
www.youtube.com/watch?v=YhYo...
The option to change console prompt position is available under the three dots button in the console toolbar, which is the last toolbar button
Toggling all the three new settings transforms the console into a single cell
The Import and Export buttons in the Settings Editor are the first two items in the toolbar panel
The workspace indicator in the open state
JupyterLab 4.4.0b1 and Notebook 7.4.0b1 are available for testing 🎉
- improved code console
- settings import/export
- better real time collaboration
- workspace indicator
- kernel subshells
Please test:
pip install --pre 'jupyterlab>=4.4.0b1'
or
pip install --pre 'notebook>=7.4.0b1'
The option to change console prompt position is available under the three dots button in the console toolbar, which is the last toolbar button
Toggling all the three new settings transforms the console into a single cell
The Import and Export buttons in the Settings Editor are the first two items in the toolbar panel
The workspace indicator in the open state
JupyterLab 4.4.0b1 and Notebook 7.4.0b1 are available for testing 🎉
- improved code console
- settings import/export
- better real time collaboration
- workspace indicator
- kernel subshells
Please test:
pip install --pre 'jupyterlab>=4.4.0b1'
or
pip install --pre 'notebook>=7.4.0b1'
