John Miller offers an overview of the Emacs IPython Notebook (EIN), a full-featured client for the Jupyter Notebook in Emacs, and shares a brief history of its development. John covers the features of EIN that make it uniquely Emacs—starting and automatically logging into a Jupyter server from inside Emacs, connecting Python buffers to a running kernel, allowing for interactive evaluation, org-mode Babel support, Emacs debugger integration, and company-mode and Jedi auto-complete integration. John then explains how he uses EIN in his own work, with a simple case study of troubleshooting activity decline of highly chlorided alumina catalyst in a pentane isomerization chemical process.
John Miller is a regional services manager in the Technology Services Division of Honeywell UOP. A chemical engineering and computer science double major, John has spent the last 20 years in the refining and petrochemicals industry trying (mostly unsuccessfully) to find a harmonious union of the two disciplines. Previously, he worked in UOP’s Field Operating Services, where he traveled the world helping refiners commission and operate UOP technology. John’s Python experience began in the late ‘90s, when he built a simple web server on the company intranet using an early incarnation of Zope. However, he’s a Lisp guy at heart. As a result, he was forced to learn that most daunting of text editors: Emacs. John found the Emacs IPython Notebook after (re)discovering IPython around version 0.11; when EIN’s creator, Takafumi Arakaki, moved on to other things and big changes in IPython required significant updates to EIN to maintain compatibility, he foolishly dived into the world of Emacs Lisp and Jupyter development and hasn’t looked back.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org