Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
If you use vim, you can also try https://github.com/hanschen/vim-ipython-cell . It works quite well
Very cool to see this – but will only be successful with great terminal plotting tools. The ones the author mentions like the matplotlib interface clearly won't do[0].
A perfect use case for unicode plotting [1] (shameless plug)
[0] https://github.com/domitry/matascii
[1] https://github.com/olavolav/uniplot
Very cool to see this – but will only be successful with great terminal plotting tools. The ones the author mentions like the matplotlib interface clearly won't do[0].
A perfect use case for unicode plotting [1] (shameless plug)
[0] https://github.com/domitry/matascii
[1] https://github.com/olavolav/uniplot
I am a big fan of https://github.com/Evizero/UnicodePlots.jl . It is impressive how useful these tools can be to track the evolution of numerical experiments and developments right on the terminal.
Here[0] is a guide that explains syncing ipynb <> py files with Jupytext. I also add ipynb to `.gitignore`. It works well, although the file browser in Jupyter becomes cluttered with every notebook file being doubled. It'd be great to hide the underlying py files.
[0] https://github.com/mwouts/jupytext/blob/master/docs/paired-n...
For editing notebooks in vim, I've created https://github.com/goerz/jupytext.vim. Note that this does not allow to run any cells, it just edits the inputs.
The motivation behind this was to have some basic interaction with existing ipynb files on a remote server without having to run the jupyter server (and set up port forwarding etc.) It's worth noting that the `jupytext.vim plugin is most useful if you're actually not running `jupytext` within jupyter; If you are, you could just directly open the .py or .md files linked to any .ipynb in your editor.
I've used `jupytext.vim` to edit existing notebooks and then run them through `jupyter nbconvert --to notebook --execute`. It's also great for refactoring: moving code from a notebook files into a module, between notebooks, or to create a new notebook as a variation of an existing one.