-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Spike: Investigate common ground between I.W. and Python REPL #23029
Comments
From your mockup screenshot, I was initially thinking of this suggestion |
Attaching meeting notes from March 7th, 2024 (feel free to add more):
|
Should be "as a controller/kernel". To expand on this, the current categories that the jupyter extension provides are these: Jupyter allows users to pick an interpreter to be used as a controller (in the python environments category) and we ensure that the required packages are installed - ipykernel/IPython. If the REPL also uses that same kernel picker (rather than perhaps just forcing the user to use the active interpreter), it would likely provide the same list of interpreters that are in Jupyter's python environments category, but selecting them would be a different experience. But I think the Python extension will have to select which controller to use when opening the IW anyway, so the user won't be in this situation unless they want to change it. |
MVP re-add cell if executed in history - aaron |
Adding issue that contains items needed for MVP: #23332 |
Discussed May 9th: If Python extension were to strive for "enter" to be the default execution mechanism for user trying to execute their Python command using IW UI (with REPL controller contributed from Python extension), we need to be able to get user's Python command inside user's text input box inside the IW UI BEFORE execute handler. |
Allow users to use Interactive Window UI with Python custom REPL controller instead of iPykernel. Closes #23175 Closes #23174 Closes #23029 Majority of: #23332 Context menu under Python for running Python REPL code using IW UI should only appear when user's ```pythonRunREPL``` experiment is enabled.
Allow users to use Interactive Window UI with Python custom REPL controller instead of iPykernel. Closes microsoft#23175 Closes microsoft#23174 Closes microsoft#23029 Majority of: microsoft#23332 Context menu under Python for running Python REPL code using IW UI should only appear when user's ```pythonRunREPL``` experiment is enabled.
Allow users to use Interactive Window UI with Python custom REPL controller instead of iPykernel. Closes #23175 Closes #23174 Closes microsoft#23029 Majority of: #23332 Context menu under Python for running Python REPL code using IW UI should only appear when user's ```pythonRunREPL``` experiment is enabled.
This document intends to capture information that pertains to or intends to distinguish between I.W. and upcoming Python native REPL. For information that is focused more solely or in a broader spectrum towards native Python REPL can be tracked here: #22674
(More to be added) Conducting spike into learning more about the current state of Interactive Window that uses iPython kernel, including target users, complains about I.W, and how I.W and notebook components and attributes can be applied towards building VS Code native Python REPL experience.
This spike plans to display and document some of the finding that represent current state of Interactive Window, Notebook and plans in moving forward for move I.W. and native Python REPL experience.
We should also note of the positive and mutually inclusive components/design/feature we would want to potentially apply in designing and implementing VS Code Native REPL.
Components/design/features that may be present in notebook, interactive window, but rather should be avoided for native VS Code REPL experience should also be listed here.
Questions that needs more research:
notebook editor
or notebook API can be used since it ison top of builtin list/tree view renderer
Actionable items going forward (more to be added):
The text was updated successfully, but these errors were encountered: