vscode-python: Debugging does not work with a conda environment
Issue Type: Bug
Behaviour
While debugging Python scripts, F5 or “Play button” gives no action - the only thing I see is bar with “stop”, “play” and “restart” buttons - but this bar just dissapear after few seconds. In terminal no output is printed. Since last successful debugging session no system updates or other apps were installed, VSCode is up-to-date. I have tried restarting VSCode and restarting computer 😉
Linked with: https://github.com/microsoft/vscode/issues/142154
Expected vs. Actual
Expected: Press F5 button runs code in debug mode. Actual: After pressing F5 button only “debug bar” appears, but code does not run at all.
Steps to reproduce:
- Open VSCode
- Open *.py file
- Press F5 or “play button” in “Run and debug” section on the left-side-bar of VSCode app window.
launch.json
{ "version": "0.2.0", "configurations": [ { "name": "Python: Current File", "type": "python", "request": "launch", "program": "${file}", "console": "integratedTerminal", "justMyCode": false } ] }Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): 3.7.7
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
- Value of the
python.languageServersetting: Pylance
User Settings
defaultLS: {"defaultLSType":"Pylance"}
downloadLanguageServer: true
envFile: "<placeholder>"
venvPath: "<placeholder>"
venvFolders: "<placeholder>"
condaPath: "<placeholder>"
pipenvPath: "<placeholder>"
poetryPath: "<placeholder>"
languageServer: "Pylance"
linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: true
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"
sortImports
• args: "<placeholder>"
• path: "<placeholder>"
formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "autopep8"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"
testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true
terminal
• activateEnvironment: true
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"
experiments
• enabled: true
• optInto: []
• optOutFrom: []
insidersChannel: "off"
tensorBoard
• logDirectory: "<placeholder>"
Extension version: 2022.0.1786462952 VS Code version: Code 1.64.0 (5554b12acf27056905806867f251c859323ff7e9, 2022-02-03T04:22:20.678Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-8250U CPU @ 1.60GHz (8 x 1800) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.90GB (8.45GB free) |
| Process Argv | –folder-uri file:///c%3A/Users/Pawe%C5%82%20Fic/Documents/MOLOS.ANALYTICS/Packages/trend_analysis --crash-reporter-id b5861c78-63a8-433f-adf7-5b3b6a81c16d |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392cf:30425750
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30433059
pythonvs932:30410667
vscop940:30404999
vsrem710cf:30416617
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 21
- Comments: 51 (14 by maintainers)
Having the same problem since the update to v2022.0.1786462952
@bernardo-suez Please check your conda version, if it is below 4.9.0 update to the latest version, and see if it helps.
same here. My situation is remote container + conda + python. Solved by degrading the python extension in VSCode to 2021.12.1559732655.
To update everyone: we have a fix merged in https://github.com/microsoft/vscode-python/pull/18451 and cherry-picked in https://github.com/microsoft/vscode-python/pull/18465 (basically we fall back to the old way of doing things if you’re running an old version of conda that doesn’t support what we need with
conda run). We hope to make a hotfix release today or tomorrow.But do note we strongly advise any of you on conda <4.9 to upgrade. The extension has been updated across the board to use
conda runto give you a better experience/results when we run tools on your behalf (i.e. your conda environment is now activated when we run tools on your behalf). As such, I would expect our support for versions of conda too old to supportconda runappropriately to quickly become best-effort.@karthiknadig’s suggestion to update Conda from 4.8 to 4.11 solved the problem.
Hey, I also noticed the problem. I attached my conda info to this message. On my windows machine with a newer version of conda I did not experience this problem, on my linux env my debugger failed. I also noticed problems switching my conda env within VSCode with the newest Python extension since yesterday, but I cannot say if this is related to this or not. My conda env was created via
conda create -n env_name.CondaInfo.txt
Thanks for looking into this issue so fast! Hope I can help with that.
I just noticed your new message while typing. So indeed the conda version in which the debugger is not working is below 4.9.0
Is anyone not a conda user?
For those that are using conda, this is probably because of https://devblogs.microsoft.com/python/python-in-visual-studio-code-february-2022-release/#improvements-when-using-anaconda . We thought we had this working but apparently there’s at least some underlying issue. While we take a look to solve this please feel free to roll back to the 2020.12 release for now and subscribe to this issue to know when we have resolved the problem.
We just published a fix for the older versions of conda. The fix is in version
2022.0.1814523869.If you are in a newer version of conda and are experiencing issues, please check the error reported by conda here https://github.com/conda/conda/issues. you can use the command in the linked comment to run the debugger from a terminal to test if it is working as expected: https://github.com/microsoft/vscode-python/issues/18436#issuecomment-1030280077
Mine worked after updating conda to
4.11.Awesome job! This new version of the Python extension works for me.
+1 for updating conda. 4.8.2 -> 4.11.0 solved it for me on Ubuntu 18.04.
@mlamarre You are running into this issue https://github.com/conda/conda/issues/10690 .
Conda info (4.10)
condainfo.txt
How the env. is created with docker RUN commands, running vscode-server inside container.
conda_creation.txt
The
adapterscript above gives a permission error trying to create a temp file in /opt not sure it means something. condaerror.txtSame for me, specifically when using a Conda environment inside a docker container. When using the System interpreter (both host’s and docker container’s) it works fine.
Had to install 2021.12.1559732655 inside the docker container’s vscode to fix it.
Also same for me.
Temporarily solved by reloading python IntelliSense to version v2021.12.1559732655.