Skip to content

automatically active environment in Python Debug Console #5915

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gunxu2000 opened this issue Jun 5, 2019 · 1 comment
Closed

automatically active environment in Python Debug Console #5915

gunxu2000 opened this issue Jun 5, 2019 · 1 comment
Labels
feature-request Request for new features or functionality

Comments

@gunxu2000
Copy link

gunxu2000 commented Jun 5, 2019 •
edited
Loading

Win7, Vscode insider, Anaconda distribution 2019.5, python extension version 2019.5.18.426.

Issue:

using "Python: Current File" launch configure to debug python script does not recognize the python environment. When do the same thing using python extension version 2019.5.17517, the environment can be recognized after pushing F5 twice. (this is because version 2019.5.17517 automatically run command conda active base in the first F5 debug session after debug failed.

Feature desired:

automatically active environment when invoke python Debug console.
@gunxu2000 gunxu2000 added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Jun 5, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 5, 2019
@brettcannon brettcannon added the triage-needed Needs assignment to the proper sub-team label Jun 5, 2019
@gunxu2000 gunxu2000 changed the title automatically active environment for debugger session when select interpreter automatically active environment in Python Debug Console Jun 5, 2019
@DonJayamanne
Copy link

Duplicate of #5664

@DonJayamanne DonJayamanne marked this as a duplicate of #5664 Jun 5, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request Request for new features or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brettcannon @DonJayamanne @gunxu2000