@tillahoffmann : this is something I really waited for. Learning Python, running scripts in Obsidian would be so great. Even if I will never do actual developing work in Obsidian.
But I can`t get it to work. Working on Windows, I don’t know what to input as path to the python interpreter. I tried everything I could think of: “C:\Users\<username>\AppData\Local\Programs\Python\Python38-32”, with all possible combinations of “/”, “\”, “//”, “\\”. The path is correct. And yes: instead of “<username>” I used my correct username.
Anyone have an update on this? I’d like to move my Jekyll site into a networked note taking platform. But I have a lot of crappy ipynb’s I’d like to also have on the site. https://rcyost.github.io/ ← how to turn this into obsidian and keeping the ipynb’s is what I am after basically.
+1 for that, having the ability to simply open natively a jupyter notebook (even without running it), and having the ability to link the markdown content would be revolutionary for computer science note taking
Currently, if you put an ipynb file into the obsidian explorer you get the json-like content. It would be great if Obsidian could preview the content like Jupyter!
You can’t run the code (not working through iframe) or edit but you can at least read it (you can actually edit, but it will not be saved). And you need to have an internet connection to load it.
The obsidian-jupyter plugin by @tillahoffmann works great for me. It’s not the right setup as a dev environment, but it’s good for noting snippets and testing the snippets, noting outputs/plots etc all within the obsidian notes.
Thanks @tillahoffmann for creating it. GitHub - tillahoffmann/obsidian-jupyter
I came across an important restriction when using this plugin. State is not maintained across cells, Variables initialized or modules imported in previous cells are not available to later cells.
It might be good for running self contained snippets on Obsidian, but not for working across multiple cells.
State is maintained in ‘Read’ mode, but not in ‘Edit’ mode. If you are testing the code you are actually writing in Edit mode, Ctrl + click the View button on the top right, and open the same panel in a ‘Read’ mode tab. Now you will be able to run what you are writing. Easy, make your updates in ‘Edit’-mode tab, run your code in ‘View’-mode tab.
While all the above-proposed solutions are great, I think what a lot of people might be after is support for the actual .ipynb file format. This would allow for developing code in a full-featured IDE and also be able to view everything in obsidian (+ added bonus would be to be able to run the cells too). Even better, being able to add wikilink support in a jupyter notebook to other parts of the vault would be amazing