Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Think of how Jupytext might use this #22

Open
choldgraf opened this issue Mar 4, 2020 · 0 comments
Open

Think of how Jupytext might use this #22

choldgraf opened this issue Mar 4, 2020 · 0 comments

Comments

@choldgraf
Copy link
Member

@mmcky 's comments about jupytext made me have a thought. Apologies if this has been obvious to others the whole time, but I think that this tool could be useful for Jupytext as well. It is common that people want to write their notebook content in text files, but view them in a notebook interface. For this, jupytext does a great job (e.g. in jupyterlab you can double-click a jupytext markdown file, and it'll open as a notebook even though it's still saving back to that markdown file).

However, one issue with only having a markdown file is you have no place to put the outputs. For users that don't want to have a 'paired' ipynb file on disk the whole time, perhaps Jupytext could leverage jupyter-cache to insert the outputs into the notebook when it is being rendered in the interface. This way you could cleanly separate outputs and content, similar to how we plan to do with Sphinx.

@choldgraf choldgraf added enhancement New feature or request discussion labels Mar 4, 2020
@chrisjsewell chrisjsewell removed the enhancement New feature or request label Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants