-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
ipynb round trip details #5398
Comments
The file that gives the stack overflow contains a raw HTML data cell that is over 2 million characters long. Note also that no stack overflow occurs with output to HTML. |
Thanks @jgm for following-up on this. I should have said that I mostly care about metadata and input cells. Indeed, Jupytext never stores output cells in the text formats (instead, outputs are preserved in a paired |
Moving stack overflow issue to #5401 (it's not specific to ipynb).
|
Should be `{}` not empty string. Partially addresses #5398.
I've fixed most of these issues, but I am getting one bad result still. This is with
and produces the markdown
which then becomes the ipynb
|
Ah. This looks like a bad interaction between the setext header syntax and the fenced div syntax. |
Got it. |
Excellent! Thanks @jgm |
From mwouts/jupytext#208
Using files in https://github.com/mwouts/jupytext/blob/1.1.0_pandoc_with_mirror_tests/tests/notebooks/ipynb_py.
Command:
Result:
Most of these issues have to do with the fact that
nbformat
(a JSON integral number 4) gets rendered in markdown YAML metadata as"4.0"
. One issue has to do with markdown YAML rendering of an empty map as the empty string instead of{}
.There's also a stack overflow, which should definitely be looked at.
The text was updated successfully, but these errors were encountered: