You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jupytext allows annotated pyy:light to render and operate as notebooks. However, editing the .py file directly and reloading from disk does not merge/sync changes to the "notebook view", but instead destroys the output cells and syntax highlighting.
We could setup the py file metadata to sync to ipynb files to enable reload, but this would mean that users must:
Open the .py file as Notebook
Save to produce the ipynb
Shutdown kernel
Open ipynb with new kernel
This just doesn't work as a workflow. Checking in the ipynbs defeats the purpose of jupytext: lint on .py file and merge into notebooks while keeping output cells and PHI out of source control.
I suspect that the settings for jupytext may be incorrect. Alos look at upcoming features of unreleased jupytext to see if this is being worked on.
Jupytext allows annotated
pyy:light
to render and operate as notebooks. However, editing the .py file directly and reloading from disk does not merge/sync changes to the "notebook view", but instead destroys the output cells and syntax highlighting.We could setup the py file metadata to sync to ipynb files to enable reload, but this would mean that users must:
This just doesn't work as a workflow. Checking in the ipynbs defeats the purpose of jupytext: lint on .py file and merge into notebooks while keeping output cells and PHI out of source control.
I suspect that the settings for jupytext may be incorrect. Alos look at upcoming features of unreleased jupytext to see if this is being worked on.
Also two pass jupytext pre-commit insanity
The text was updated successfully, but these errors were encountered: