Removing the notebookDeprecated proposal
See original GitHub issueThe notebookDeprecated
api proposal is currently not on track for finalization. It only contains a single property NotebookCellOutput.id
, which we believe is no longer useful or needed
We plan on removing this proposal it once all current consumers have migrated off it. Here’s the current list:
- Jupyter @rchiodo @DonJayamanne
- Data Wrangler @pwang347
- Dot Net Interactive @brettfo, @colombod
Please check if your extension is using this api and if you have any concerns migrating off of it
Issue Analytics
- State:
- Created a year ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Removing the notebook concat text document API proposal · Issue ...
We plan to remove this proposed API once all current consumers have migrated off of it. The only known consumers today are: Jupyter...
Read more >"This editor is deprecated and we'll remove it after 1.59 of VS ...
1 Answer 1 · Close the ipynb file · Go to the VSCode Explorer window on the left · Right click on the...
Read more >Restoring the Executability of Jupyter Notebooks by Automatic ...
we propose RELANCER, an automatic technique that restores the executability of broken Jupyter Notebooks, in near real time, by upgrading deprecated APIs.
Read more >deprecation policy - Google Groups
and, once the time is up, actually remove the deprecated stuff. Stupid example: say I want to rename the matrix method "echelonize" to...
Read more >Deprecate and remove support for a supported operating system
You must tell customer-facing teams about the deprecation and upcoming removal of support for the OS. Announce the deprecation in the following Slack...
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
id
is useful to find ext host output from renderer (command, actions, etc)id
is random and doesn’t fit into model as nicelyI think the assumption that we don’t want metadata in the output could be challenged. We already put metadata in the kernel info. Adding it to the output doesn’t seem bad to me.
And writing metadata need only happen when we update an output. Output without metadata.ids could just skip supporting the plot viewer.
Additionally we might not even need it. You could hash the contents of the image and when clicking the plot viewer or plot save button, pass the hash of the image. The extension side code could just look for this image in the output data.