question-mark
Stuck on an issue?

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.

ERROR conda.cli.main_run:execute(33): Subprocess for 'conda run [' XXXXXXXXXX']' command failed. (See above for error)

See original GitHub issue

Issue Type: Bug

ERROR conda.cli.main_run:execute(33): Subprocess for ‘conda run [‘python’, ‘/{dir_loc}/python_file.py’]’ command failed. (See above for error)

Steps to reproduce:

  1. Update vscode-python to version 2022.2.1924087327

Diagnostic data

  • Python version (& distribution if applicable, e.g. Anaconda): 3.9.5
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
  • Value of the python.languageServer setting: Default
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: false
• 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.2.1924087327 VS Code version: Code 1.65.0 (b5205cc8eb4fbaa726835538cd82372cc0222d43, 2022-03-02T11:12:36.248Z) OS version: Linux x64 5.13.0-30-generic Restricted Mode: No

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30433507
vsclayoutctrc:30448490
vsrem710:30416614
dsvsc008:30440022
pythonvsnew555:30442236
vsbas813:30436447
vscscmwlcmc:30438804
helix:30440343

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:18

github_iconTop GitHub Comments

23reactions
rafattusharcommented, Mar 7, 2022

For now, I resolved this issue by switching back to previous version of this vscode-Python extension. image Click Downward arrow beside ‘uninstall’ button > Install another version > Select second version 2022.0.1814523869 and restart the VSCode resolve this issue.

7reactions
chrisniu7commented, Mar 8, 2022

For now, I resolved this issue by switching back to previous version of this vscode-Python extension. image Click Downward arrow beside ‘uninstall’ button > Install another version > Select second version 2022.0.1814523869 and restart the VSCode resolve this issue.

same issue,now i revolve this problem,thanks

Read more comments on GitHub >

github_iconTop Results From Across the Web

Your shell has not been properly configured to use 'conda ...
However, I can't activate with the following error. CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
Read more >
Known issues — Anaconda Platform 5.6.0 documentation
If you attempt to download a file from within a JupyterLab project running on Chrome, you may see a Failed/Forbidden error, preventing you...
Read more >
conda-build Documentation
See Troubleshooting a sample issue if the conda-build command fails. If you receive an error with SDK on macOS, review our resources.
Read more >
How to Setup Your Python Environment for Machine Learning ...
3. Start and Update Anaconda · 1. Open a terminal (command line window). · 2. Confirm conda is installed correctly, by typing: 1....
Read more >
How to start Julia REPL in VS CODE (Insiders) in specified ...
I use VS CODE 1.58.0 (Insiders) and SSH connection to connect to Ubuntu 18.04.5 LTS and conda environment (env name: base).
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found