Separate Directory Paths for md, py and ipynb files
See original GitHub issueI have a workflow where I would like to be able to use md
or py
file representations for version control, with a separate “demonstration” directory with rendered notebooks grabbed every so often as a showcase.
To keep things tidy, it would be useful for different filetypes to live down different paths, for example py/
or notebooks/
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Import py file in another directory in Jupyter notebook
So I want to keep the functions.py file in /user/project but be able to call it from an . ipynb file in /user/project/model1...
Read more >Configuration - Jupytext documentation - Read the Docs
For instance, with the pairing above, a notebook with path /home/user/jupyter/notebooks/project1/example.ipynb will be paired with the Python file /home/user/ ...
Read more >Version Control With Jupyter Notebook | by Shinichi Okada
Creating a demo repo. First, let's create a new Jupyter Notebook file with the following codes. x = np.arange(-3, 3, 0.1) y =...
Read more >Jupyter notebooks as Markdown documents or Python scripts
Using a specialized diff tool like nbdime will make the diffs easier to navigate, but in the end, the single notebook file (i.e....
Read more >Types of content source files - Jupyter Book
Any other file type can be auto-converted before execution by assigning it a custom Python function, for example those provided by the Jupytext...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mwouts tested now, the error is gone! Thanks
I’ll close this issue, as the functionality has been tested by several users. If anyone feels the documentation can still be improved, they should submit a PR on the README with the suggested improvements. Thanks!