summaryrefslogtreecommitdiff
path: root/content/blog/jupyterlab-notebook-file-oneliner/index.rst
diff options
context:
space:
mode:
authorjaseg <git@jaseg.de>2025-06-30 15:35:25 +0200
committerjaseg <git@jaseg.de>2025-06-30 15:35:25 +0200
commit16655c00e0a84f6bfe58870c918fbfc016fe58ec (patch)
treed410d2203b32b005ebb601e766a40f280ed8d32c /content/blog/jupyterlab-notebook-file-oneliner/index.rst
parenta324ba7b649840c16d365b757b19db2849991f11 (diff)
downloadblog-16655c00e0a84f6bfe58870c918fbfc016fe58ec.tar.gz
blog-16655c00e0a84f6bfe58870c918fbfc016fe58ec.tar.bz2
blog-16655c00e0a84f6bfe58870c918fbfc016fe58ec.zip
Fix hugo layout in hugo > ~0.130.0
For some reason, newer hugo versions have trouble with .summary, and on some pages where .summary is not defined in the page header metadata, when rendering the page as a preview card, hugo swallows the card's closing </div> tag. Such a weird bug, we now just work around it by explicitly setting the .summary meta on pages that cause this bug(?) to surface.
Diffstat (limited to 'content/blog/jupyterlab-notebook-file-oneliner/index.rst')
-rw-r--r--content/blog/jupyterlab-notebook-file-oneliner/index.rst21
1 files changed, 21 insertions, 0 deletions
diff --git a/content/blog/jupyterlab-notebook-file-oneliner/index.rst b/content/blog/jupyterlab-notebook-file-oneliner/index.rst
new file mode 100644
index 0000000..5a543de
--- /dev/null
+++ b/content/blog/jupyterlab-notebook-file-oneliner/index.rst
@@ -0,0 +1,21 @@
+---
+title: "Getting the .ipynb Notebook File Location From a Running Jupyter Lab Notebook"
+date: 2025-06-29T23:42:00+01:00
+summary: >
+ If you need to get the path of the ipynb file in a running #Jupyter notebook, this one-liner will do the trick. It
+ seems chatgpt is confused, and a bunch of other approaches on the web look fragile and/or unnecessarily complex to
+ me.
+---
+
+If you need to get the path of the ipynb file in a running #Jupyter notebook, this one-liner will do the trick. It seems
+chatgpt is confused, and a bunch of other approaches on the web look fragile and/or unnecessarily complex to me.
+
+.. code:: python
+
+ import sys
+ Path(json.loads(Path(sys.argv[-1]).read_bytes())['jupyter_session'])
+
+The way this works is that for each notebook, jupyter starts a python "kernel" process that actually runs the notebook's
+code. That kernel gets a json file with info on the notebook's location on the disk passed through its command line.
+Since we're running code in that exact python process, we can just grab that json file from sys.argv, and read it
+ourselves.