fzuhl
November 19, 2025, 11:55pm
1
The python console in Positron Pro may have its features, but please include, as an option, the feature of adding the 'interactive' python.
julia
November 20, 2025, 2:55am
2
Thank you for this feedback!
Instead of the Jupyter interactive window, Positron has its own fully featured interactive console. We are totally committed to the fully interactive Positron console for use cases where you might in VS Code use the Jupyter interactive window. Can you share what you miss about the interactive window compared to the console?
We are tracking console improvements in the styling of inputs and outputs here:
opened 07:43AM - 27 Jun 24 UTC
enhancement
area: console
I find it hard to visually parse the console output because inputs and outputs a… re styled exactly the same way. If we had a slightly different colour, or maybe bold inputs, and a bit of spacing between the end of an output and the next input (ideally this styling would be user-configurable), it would be easier to distinguish units of work in the console. The following should feel less like a wall of text and more like structured text:
<img width="313" alt="Screenshot 2024-06-27 at 09 21 52" src="https://github.com/posit-dev/positron/assets/4465050/0ae2afe3-a6f1-48b5-a7e2-d92e4a0c99f8">
The warp project takes this idea quite fare by splitting the output in "blocks": https://www.warp.dev. IIRC our treatment of errors is inspired by this idea and indeed the red box improves the structure of the output, though it still feels like the red box sticks equally to the text preceding it as to the text following it because of the lack of spacing:
<img width="372" alt="Screenshot 2024-06-27 at 09 32 25" src="https://github.com/posit-dev/positron/assets/4465050/b75dbc57-0176-490f-a79c-9db07288ea58">
Relatedly, it would be very helpful to have navigation commands across inputs in the console to make it easy to go back in the console history and inspect previous outputs.
Is that what you miss? Or something else?