Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
python.datascience.execSelectionInteractive is very slow compared to python.datascience.runcurrentcell
See original GitHub issueBug: python.datascience.execSelectionInteractive is very slow compared to python.datascience.runcurrentcell
Steps to cause the bug to occur
- Assign python.datascience.execSelectionInteractive to unique keybinding without when expression to rule out keybinding slowness
- Assign python.datascience.runcurrentcell to keybinding
- Compare the response time of two different actions on single line
Actual behavior
python.datascience.execSelectionInteractive is observably quite slow, especially compared to python.datascience.runcurrentcell which is instant.
Expected behavior
python.datascience.execSelectionInteractive should take the same amount of time as python.datascience.runcurrentcell
^ In this screenshot I pressed
python.datascience.execSelectionInteractivepython.datascience.runcurrentcellpython.datascience.execSelectionInteractivepython.datascience.runcurrentcell
Much more logs are displayed when pressing python.datascience.execSelectionInteractive
Your Jupyter and/or Python environment
- Jupyter server running: Local
- Extension version: 2020.3.71659
- VS Code version: 1.43.2
- Setting python.jediEnabled: false
- Python and/or Anaconda version: 3.8.2
- OS: Archlinux
- Virtual environment: venv
Developer Tools Console Output
Full output: console.log
My guess
It seems like python.datascience.execSelectionInteractive is trying to find interpreters every time it runs while python.datascience.runcurrentcell does not. It also seems like finding interpreters is slow, this would explain why starting up my notebook can be pretty slow; but I don’t mind that as long as it runs well…
I prefer python.datascience.execSelectionInteractive so it’d be nice if it wasn’t slow 😦
Thank you for the awesome extension regardless.
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @u8sand. Thank you for your feedback, it is very well researched.
execSelectionInteractivedoes indeed end up looking for all the interpreters. We’ll discuss this issue in our next triage.Execution time of the cell didn’t change, UI responsiveness changed (see screenshot).
Checking now it was in-fact fixed–thanks! 👍