Skip to content
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

Support cell sync between python script and interactive window. (was: python code with cell magic and "compiled" notebook split-view) #4721

Closed
tobiasbj opened this issue Feb 9, 2021 · 5 comments
Assignees
Labels
feature-request Request for new features or functionality interactive-window Impacts interactive window

Comments

@tobiasbj
Copy link

tobiasbj commented Feb 9, 2021

Note: This feature request might have been created before, but I didn't not find it while searching. I however did not know which key words were the most fitting.

I would like a feature like they have in intellij where you can have the python code (with cell magic and markdown) of the notebook on one side and the compiled notebook on the other side.

Here is an example from intellij
image
( The picture is from here )

It would be nice to actually also add the code block for each of the code output cells to, so basically recreating a standard notebook from python code with cell magic.

This is a "magic" feature which would make me use notebooks much more than I do, because using the standard "compiled" notebooks for coding is quite slow imo.

Feel free to suggest a better name for this feature suggestion.

@IanMatthewHuff
Copy link
Member

@tobiasbj Thanks for the suggestion. Just to make sure that I'm tracking your suggestion correctly we currently have the two following options in VS Code

  1. A standard notebook interface with output interleaved with code cells
  2. The interactive window, where cell markers and magics live in .py files. And the output history of what you have executed is hosted in a split window.

What you would like is more like our current interactive window. But instead of the split interactive window hosting a history of execution (if you run a cell five times in a row you would see 5 outputs in the window) the cells would be tied one to one with a single output cell per code cell in the .py file. Is that a correct understanding?

@tobiasbj
Copy link
Author

@IanMatthewHuff Yes, that is exactly what I'm suggesting (and hoping for). Sorry for my poor explanation.

@IanMatthewHuff
Copy link
Member

IanMatthewHuff commented Feb 10, 2021

@tobiasbj No your suggestion was quite clear. Just with user enhancements I always like to make sure that we've confirmed what the user is looking for to make sure that we exactly understand them.

I personally do like this suggestion. I generally prefer working with the Interactive Window myself and using .py files and the 1:1 mapping sounds like a good suggestion on this. I could see times that I would want the current "history" behavior and times that I would want the 1:1 so maybe it could be a mode type of thing.

@greazer greazer changed the title python code with cell magic and "compiled" notebook split-view Support cell sync between python script and interactive window. (was: python code with cell magic and "compiled" notebook split-view) Feb 16, 2021
@greazer greazer added the interactive-window Impacts interactive window label Aug 3, 2021
@DonJayamanne
Copy link
Contributor

Possibly a duplicate of #1240

@greazer greazer added feature-request Request for new features or functionality and removed enhancement labels May 4, 2022
@amunger
Copy link
Contributor

amunger commented Dec 6, 2022

closing as duplicate

@amunger amunger closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality interactive-window Impacts interactive window
Projects
None yet
Development

No branches or pull requests

6 participants