-
Notifications
You must be signed in to change notification settings - Fork 290
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
Interactive Window code entry cell should not have an execution count #3682
Comments
Spyder works this way. It shows what the new execution count would be. |
Although personally I'd rather just have the >>> instead of the count. Count seems weird to me too. |
Yeah, I'd seen Spyder do that. My opinion count = execution seems better. Not a big deal if we want to look more Spyder like, but I'd prefer looking like Jupyter. |
In our case the execution is always sequential, so it probably isn't a big deal. It definitely matters in the case of Jupyter Notebooks, as cell executions can be out of order. |
Execution count happens when something actually executes. The code input section should not have an execution count before it actually executes:
The text was updated successfully, but these errors were encountered: