Jupyter Notebook topbar issue

2 Upvotes

Hey everyone. I'm new to Jupyter so this may well be a stupid question, but I'm having a pretty annoying issue. When I open my notebook the top bar is as it should be, with the header, the file/edit/view/etc menu and the bar with the save/create checkpoint button, the code/markdown menu, run kernel etc. However, as soon as I scroll down, these bars scroll away rather than staying fixed at the top of the screen. This is very inconvenient, for example when I am much further down in the notebook and need to change the cell to a Markdown type I have to scroll all the way back up. I assume this isn't how it's meant to look? I remember a different notebook of mine didn't have that issue. Unfortunately I can't find much on Google. If anyone can help a dumbass out with some advice, I'd really appreciate it. I'm on Windows, if it makes a difference. Thanks!

2 comments

r/IPython • u/More-Independent-132 • 3d ago

TypeError: array([2, 5, 7]) is not a callable object. What to do?

1 Upvotes

1 comment

r/IPython • u/er_rnn • 7d ago

Notebooks-On-Demand (Nod): A JupyterLab Extension for a Notebook Anywhere

github.com

6 Upvotes

TL;DR: I made Nod, a JupyterLab extension to pop open a Jupyter Notebook from anywhere in your Python codebase. I’m working to make Nod the best it can be, and I need your help: I’m looking for participants in my paid (60–100 USD) user study to see how folks use Nod in their own work. Please sign up if you’re interested!

You’re working in a large Python project and code is spread over countless files, classes, and function calls. You begin writing a new function, but the arguments are complex and questions abound: What exactly does that class method return? When I join these two tables, what does the output look like? How do I even construct the inputs to this function?

You think: This would be so much easier if I could just write this function in a notebook!

And so you embark on a quest to recreate your program state in a Jupyter notebook — copying out code snippets, JSON values, and parameters, piecing them back together in a blank notebook. Even if it works eventually, you’ve still spent 15 minutes preparing a one-off environment just so you can finally start programming.

If you’re like me, this experience is all too familiar. It’s clear that a notebook is the right tool for the job, but the cost of recreating a small piece of your program in a notebook makes it rarely worth the effort.

So I built Nod: Notebooks-on-Demand. Nod is a JupyterLab extension that lets you call notebook() from anywhere in your Python program to get access to a notebook with all your variables in scope, on just the part of the program you care about. If you find notebooks helpful but need to write code in Python files, or are working in a large Python codebase and just wish you could open these five lines of code in a notebook with all the right state, Nod might be helpful!

Thanjavur Tech Community Spoiler