Debugger does not show "View Value in Data Viewer".
See original GitHub issueEnvironment data
- VS Code version: 1.54.0-insider
- Extension version (available under the Extensions sidebar): v2021.1.502429796
- OS and version: Linux x64 5.10.4-051004-generic
- Python version (& distribution if applicable, e.g. Anaconda): CPython
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): pyenv
- Relevant/affected Python packages and their versions: python-3.9.1, pandas-1.2.1
- Relevant/affected Python-related VS Code extensions and their versions: Jupyter extension 2020.12.414227025
- Value of the
python.languageServer
setting: Pylance
Expected behaviour
According to the January 2021 release, when debugging a python file, right-click on a dataframe should show “View in Data Viewer”
Actual behaviour
Right-click on dataframe variable does not show “View in Data Viewer”
Steps to reproduce:
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
> conda --version
> python3.7 ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
Starting Pylance language server.
Python interpreter path: ~/.pyenv/versions/py39/bin/python
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py flake8 --format=%(row)d,%(col)d,%(code).1s,%(code)s:%(text)s ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py flake8 --format=%(row)d,%(col)d,%(code).1s,%(code)s:%(text)s ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py mypy --ignore-missing-imports --follow-imports=silent --show-column-numbers ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py mypy --ignore-missing-imports --follow-imports=silent --show-column-numbers ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py flake8 --format=%(row)d,%(col)d,%(code).1s,%(code)s:%(text)s ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py flake8 --format=%(row)d,%(col)d,%(code).1s,%(code)s:%(text)s ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py mypy --ignore-missing-imports --follow-imports=silent --show-column-numbers ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py mypy --ignore-missing-imports --follow-imports=silent --show-column-numbers ~/src/python-project-skeleton/notebooks/haha.py
cwd: ~/src/python-project-skeleton
##########Linting Output - mypy##########
##########Linting Output - flake8##########
Error 2021-02-12 18:18:23: Failed to get interpreter information for '/home/verdi/.pyenv/shims/python3.9' [Error: Command failed: "/home/verdi/.pyenv/shims/python3.9" "/home/verdi/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py" "/home/verdi/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/interpreterInfo.py"
pyenv: python3.9: command not found
The `python3.9' command exists in these Python versions:
3.9.1
3.9.1/envs/py39
py39
Note: See 'pyenv help global' for tips on allowing both
python2 and python3 to be found.
at ChildProcess.exithandler (child_process.js:312:12)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket.<anonymous> (internal/child_process.js:443:11)
at Socket.emit (events.js:315:20)
at Pipe.<anonymous> (net.js:674:12)] {
killed: false,
code: 127,
signal: null,
cmd: '"/home/verdi/.pyenv/shims/python3.9" "/home/verdi/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/pyvsc-run-isolated.py" "/home/verdi/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/interpreterInfo.py"'
}
##########Linting Output - flake8##########
##########Linting Output - mypy##########
Success: no issues found in 1 source file
> conda --version
> ~/.pyenv/versions/py39/bin/python ~/.vscode-insiders/extensions/ms-python.python-2021.1.502429796/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/src/python-project-skeleton -s --cache-clear
cwd: ~/src/python-project-skeleton
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (4 by maintainers)
Top Results From Across the Web
VS Code no longer showing option to view DataFrame in Data ...
I'm working with pandas in VS Code and I've been using the View value in Data Viewer option to look at my Data...
Read more >View variable values in data tips - Visual Studio (Windows)
Use data tips to conveniently view information about variables, including arrays and structures, while debugging. You can also modify ...
Read more >Debugging Python Code on VSCode with Data Viewer (Pandas)
In the latest Python for VSCode Update, VSCode brings Data Viewer for Python Objects while Debugging Native Python Code. This is similar to ......
Read more >Python in VS Code Adds Data Viewer for Debugging
Then, you can just add a breakpoint after the line of the variable you want to inspect, hit F5 and select Python File...
Read more >Debugger. Data Views | PyCharm Documentation - JetBrains
If they don't contain explicit method invocations, the debugger evaluates them and shows the corresponding values in the Variables view.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@manojbaishya that makes sense! Most of the features that we believe to be interesting for Python developers from the Jupyter extension are in the Data Science section of our documentation.
Hey @luabud, thanks for the suggestion. I tried doing that. I also tried reinstalling/disabling pylance and python extension and no luck. But after updating to
vscode==1.59.1
the issue just disappeared and the View Value in Data Viewer option now shows on the debug variables. If it helps I am using vscode server remote development. Also the other issue I stated disappeared after the update. I will report it if I see it any time in future.