microsoft / vscode-jupyter

VS Code Jupyter extension
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter
MIT License
1.27k stars 284 forks source link

[Suggestion] Add for Jupyter Notebook's Python Markdown #4946

Open gusbemacbe opened 3 years ago

gusbemacbe commented 3 years ago

Hello,

I refer to the article here about Python Markdown.

With this extension enabled on Jupyter Notebook, it allows to render the variable on a Markdown cell from a Python cell. Only Jupyter Notebook supports it, but VSCode Insiders does not support even if I always trust the notebook. You can compare two GIFs:

1 2

gusbemacbe commented 3 years ago

@rchiodo, done.

rchiodo commented 3 years ago

Thanks for the suggestion. We'll leave this open to see how many people up vote it.

bruno-salmito commented 3 years ago

Greate.

fabriciolak commented 3 years ago

Cool

gusbemacbe commented 2 years ago

Any news, @rchiodo ?

DonJayamanne commented 2 years ago

Unfortunately this hasn't been priotized yet. We work on issues based on upvotes, have longest upvote this

SYNiMAK commented 2 years ago

👍

DonJayamanne commented 2 years ago

Note for internal use:

Possibly a candidate for powertoys extension. However blocked on this feature request https://github.com/microsoft/vscode/issues/121256

SYNiMAK commented 2 years ago

Super keen to see this in VS code, which ever way.

gusbemacbe commented 2 years ago

Possibly a candidate for powertoys extension.

@DonJayamanne, it is exclusive of Windows 10 and 11. :-/

DonJayamanne commented 2 years ago

im referring to the following extension, currently under development https://github.com/microsoft/vscode-jupyter-powertoys

piggjf commented 2 years ago

Upvoting via comment. If there's an actual button to click, please share its location.

Coming from R where I could `r var.name` stochastically generated variables to Jupyter has been a bit of an adjustment. My writing style is suffering and reminds me of the work that I produced back in third grade.

ManuelWIAS commented 1 year ago

Is this working now ?

drorata commented 1 year ago

Seems like it doesn't. I guess the need is still there.

BengtDahlgrenGeo commented 1 year ago

It would be a great feature for industries constantly creating reports that are very similar. We switched to Jupyter Notebook because of the lack of this feature.

gaardhus commented 1 year ago

This is IMO a very important feature when utilizing Notebooks for what they really should be: writing report like documents. Not being able to reference a variable within a markdown cell makes this much more cumbersome.

t-fourcade-isp commented 1 year ago

I fully agree with the previous comments. In my company it is this missing feature that hold us back from switching to vscode notebook (we keep working with jupyterlab even if we all agree that vscode is overall better).

gaardhus commented 1 year ago

It seems that Quarto has this (somewhat) figured out in their next release: https://github.com/quarto-dev/quarto-cli/pull/6190

DonJayamanne commented 1 year ago

Quarto isn't displaying markdow the same way Jupyter does, they are pre-evaluating the cells and then rednering them, in Jupyter its completely diferent, i.e. if you update the variable then the markdown has to be updated, where as in quarto the mardown cell is generated after the variable has been initialized and its actual code thats executed.

DonJayamanne commented 1 year ago

Does anyone here use Jupyter Lab, if so what is the extension in Jupter Lab that makes this possible? Thanks

gaardhus commented 1 year ago

I havn't been able to find a solution that works in Jupyter Lab either, only the following for Jupyter Notebooks https://stackoverflow.com/a/52874352/9811508

t-fourcade-isp commented 1 year ago

There is two solutions, one for jupyter notebook and one for jupyterlab:

I tested both and they work well in their own environments.

decimad commented 1 month ago

I cannot understand why this common-sense must-have feature needs some determined thumbs-up count since 3 years to be considered for being taken out of the backlog while the extension supports so many nonsense features that nobody will hardly require anytime... I'm forced to copy and paste latex stuff from python output into markdown cells since the beginning and will now switch to jupyterlab because of this. Given the huge amount of effort that must have been spent on this extension, without question, it's a shame.