Jupyter Notebook
Jupyter Notebook is an interactive computing environment that supports mixing code, execution results, visualizations, and Markdown text within a single document. It is a standard development tool in the fields of data science and machine learning.
Core Facts
The name Jupyter is a portmanteau of Julia, Python, and R, three scientific computing languages.
The course project uses Jupyter Notebook as its primary teaching medium.
Warp adopts Block-based Navigation, encapsulating each command execution and its output as an independent block, drawing on the Cell concept from Jupyter Notebook.
Timeline (last 90 days)
在 OpenAI Agents SDK 中，Runner.run_sync 是同步调用方式，会立即返回响应，但无法在 Jupyter Notebook 中运行，因为 Notebook 自身已运行着事件循环，嵌套启动新循环会抛出 'This event loop is already running' 错误。
The author believes notebooks will not disappear in the short term, and their role will evolve from 'a place to write code' to 'a workbench where human intent and Agent execution converge.'
Jupyter has long been criticized for the 'implicit state' problem, where out-of-order cell execution leads to irreproducible results.
The core value of Notebook is a reproducible reasoning trace that records the input, output, and intermediate visualizations of every step.
Code cells yield the same result every time they are executed under a fixed random seed, whereas a pure 'prompt → result' approach introduces the non-determinism of large models.
The core structure of Jupyter Notebook has Markdown cells handling narration, Code cells handling execution, and output embedded inline immediately after the code.
The design philosophy of Jupyter Notebook can be traced back to around 2011, with its inspiration drawn from the concept of 'Literate Programming' proposed by Donald Knuth in 1984.
The Python interactive interpreter, Jupyter Notebook, and Node.js console are all typical REPL implementations.
Traditional Jupyter Notebooks have execution order dependency issues, where cells can be run out of sequence, causing the same Notebook to potentially produce different results at different times or on different machines, making reproducibility difficult
The popularization of Jupyter Notebook and the rise of the Hugging Face ecosystem have to some extent bridged the knowledge gap between research and engineering.
20 more timeline events
All Facts (20)
The name Jupyter is a portmanteau of Julia, Python, and R, three scientific computing languages.
90%VerifiedThe course project uses Jupyter Notebook as its primary teaching medium.
65%VerifiedWarp adopts Block-based Navigation, encapsulating each command execution and its output as an independent block, drawing on the Cell concept from Jupyter Notebook.
65%Unverified该项目以Jupyter Notebook为主要载体，开发者可以逐个Cell执行
90%UnverifiedGitHub上有超过1000万个Jupyter Notebook文件
70%UnverifiedJupyter Notebook's underlying architecture uses a Kernel architecture, where the front-end interface communicates with the back-end computing kernel via WebSocket.
60%UnverifiedJupyter Notebook currently supports more than 100 programming language kernels.
60%UnverifiedTop journals such as Nature have begun requiring authors to submit runnable Notebooks as supplementary materials for papers.
60%UnverifiedJupyter Notebook originated from the IPython project in 2011, led by Fernando Pérez.
60%Unverified在 OpenAI Agents SDK 中，Runner.run_sync 是同步调用方式，会立即返回响应，但无法在 Jupyter Notebook 中运行，因为 Notebook 自身已运行着事件循环，嵌套启动新循环会抛出 'This event loop is already running' 错误。
50%UnverifiedThe core value of Notebook is a reproducible reasoning trace that records the input, output, and intermediate visualizations of every step.
50%UnverifiedJupyter has long been criticized for the 'implicit state' problem, where out-of-order cell execution leads to irreproducible results.
50%UnverifiedThe design philosophy of Jupyter Notebook can be traced back to around 2011, with its inspiration drawn from the concept of 'Literate Programming' proposed by Donald Knuth in 1984.
50%UnverifiedThe core structure of Jupyter Notebook has Markdown cells handling narration, Code cells handling execution, and output embedded inline immediately after the code.
50%UnverifiedCode cells yield the same result every time they are executed under a fixed random seed, whereas a pure 'prompt → result' approach introduces the non-determinism of large models.
50%UnverifiedThe Python interactive interpreter, Jupyter Notebook, and Node.js console are all typical REPL implementations.
50%UnverifiedTraditional Jupyter Notebooks have execution order dependency issues, where cells can be run out of sequence, causing the same Notebook to potentially produce different results at different times or on different machines, making reproducibility difficult
50%UnverifiedThe popularization of Jupyter Notebook and the rise of the Hugging Face ecosystem have to some extent bridged the knowledge gap between research and engineering.
50%UnverifiedInference code in a Notebook is typically executed in a single-threaded, single-request manner, and without asynchronous processing or multi-replica mechanisms, timeouts or crashes will occur under high load.
50%UnverifiedIn Jupyter Notebook or certain framework environments where the event loop is already running, directly calling asyncio.run() will raise a 'This event loop is already running' error; the common fix is to patch it using the nest_asyncio library (nest_asyncio.apply()).
50%