From Jupyter Notebooks to a Python Package: The Best of Both Worlds
Formal Metadata
| Title | From Jupyter Notebooks to a Python Package: The Best of Both Worlds |
|
| Title of Series | |
| Number of Parts | 141 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | A Jupyter notebook is quite handy for rapid REPL (Read-Eval-Print-Loop) style tasks such as exploratory data analysis and data science. However, we would feel
deficiencies in proper SW engineering supports at some point as the notebook grows to have larger and more complicated code. It is because the Jupyter notebook lacks several important features including code sharing, refactoring support,
version control and advanced editing. Fortunately, traditional full-fledged IDEs,
such as _VS Code_ or _PyCharm,_ are available at hand and they support
these lacking features very well.
Then, why don’t we take advantage of the best of both worlds?
In this beginner-level hands-on talk, I will demonstrate how to
transform Jupyter notebook workflows to a proper Python package using _VS Code._
I will also introduce several basic but essential refactoring recommendations. By doing so, you can use the package for several notebooks
and even share with your colleagues and friends. |
|