rc2 error: "Format specifiers should include the current notebook format"
See original GitHub issueWhen I move from rc1 to rc2 with the following juyter_notebook_config.py
c.NotebookApp.contents_manager_class = "jupytext.TextFileContentsManager" # noqa
c.ContentsManager.default_jupytext_formats = "ipynb,python//py:percent" # noqa
c.ContentsManager.default_notebook_metadata_filter = "all"
c.ContentsManager.default_cell_metadata_filter = "all"
I see an error message as in the subject line (white text, orange background)
“Format specifiers should include the current notebook format”
Happy to provide more information if a simple notebook doesn’t reproduce this for you.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Jupyter extension for Jupytext · Issue #86 · mwouts ... - GitHub
The documentation on how to distribute a notebook extension is here. ... rc2 error: "Format specifiers should include the current notebook ...
Read more >The Notebook file format — nbformat 5.7 documentation
The official Jupyter Notebook format is defined with this JSON schema, which is used by Jupyter tools to validate notebooks. This page contains...
Read more >Aligning strings within string.Format and interpolated strings
To right-align formatted strings as we have here, you can use an alignment component in your string.Format format specifiers.
Read more >How do I convert IPython v3 notebooks to Jupyter v4?
I have a ton of old v3 IPython notebooks on my local filesystem. After upgrading IPython to Jupyter, I am getting an annoying...
Read more >What's new in F# 6 - .NET Blog
NET Interactive Notebooks in Jupyter or VS Code ... F# 6 adds the %B pattern to the available format specifiers for binary number...
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
yes that fixed it – thx!
Philip, there is a new rc available:
Can you please confirm that it solves this issue? Thanks