Skip to content

Do not use conda run when launching a debugger - #18858

Merged
Kartik Raj (karrtikr) merged 4 commits into
microsoft:mainfrom
karrtikr:condaout
Apr 4, 2022
Merged

Kartik Raj (karrtikr) merged 4 commits into
microsoft:mainfrom
karrtikr:condaout

Conversation

@karrtikr

@karrtikr Kartik Raj (karrtikr) commented Apr 4, 2022 •

Copy link
Copy Markdown

Closes #18847

We get the conda executable to use using shellExec, but the DebugAdapterExecutable does not use a shell when launching the executable, and hence fails. For now, the solution is to not use a conda executable when launching a debugger.

Opened #18859 to investigate if it's possible to get the conda executable using exec instead of shellExec.

@karrtikr Kartik Raj (karrtikr) added the skip tests Updates to tests unnecessary label Apr 4, 2022
@karrtikr
Kartik Raj (karrtikr) marked this pull request as draft April 4, 2022 22:53
This reverts commit 0ade929.
@karrtikr
Kartik Raj (karrtikr) marked this pull request as ready for review April 4, 2022 23:01
@karrtikr
Kartik Raj (karrtikr) merged commit 0affe01 into microsoft:main Apr 4, 2022
@karrtikr
Kartik Raj (karrtikr) deleted the condaout branch April 4, 2022 23:14
Kartik Raj (karrtikr) pushed a commit to karrtikr/vscode-python that referenced this pull request Apr 6, 2022
* Do not use conda run when launching a debugger

* News

* Only build VSIX

* Revert "Only build VSIX"

This reverts commit 0ade929.
Kartik Raj (karrtikr) pushed a commit that referenced this pull request Apr 6, 2022
* Ensure `conda info` command isn't run multiple times during startup when large number of conda interpreters are present (#18808)

* Wrap file paths containg an ampersand in double quotation marks for running commands in a shell (#18855)

* If a conda environment is not returned via the `conda env list` command, resolve it as unknown (#18856)

* If a conda environment is not returned via the conda env list command, resolve it as unknown

* News entry

* Fix unit tests

* Do not use conda run when launching a debugger (#18858)

* Do not use conda run when launching a debugger

* News

* Only build VSIX

* Revert "Only build VSIX"

This reverts commit 0ade929.

* Fixes support for python binaries not following the standard names (#18860)

* Fixes support for python binaries not following the standard names

* news

* Remove comment

* Do not validate conda binaries using shell by default (#18866)

* Do not validate conda binaries using shell

* Fix tests

* Fix lint

* Fix tests

* Ensure string prototypes extension extends are unique enough (#18870)
Wes McKinney (wesm) pushed a commit to posit-dev/positron that referenced this pull request Mar 28, 2024
…on#18858)

* Do not use conda run when launching a debugger

* News

* Only build VSIX

* Revert "Only build VSIX"

This reverts commit 0ade929b400912a97f93099510950ba7d81779a2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip tests Updates to tests unnecessary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Python Debugger won't launch for conda envs

1 participant