We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Testing #20538
In the TPI's Case II & III, I notice that base gets activated anyways
The text was updated successfully, but these errors were encountered:
@andreamah This seems expected as auto activate base is configured to true.
Manual activation isn't required in those cases.
Sorry, something went wrong.
Didn't case II and III have something like
Open a Python file to activate the extension, ensure the base environment is not auto-selected at startup.
?
So then I wouldn't expect an automatic activation in that case?
Ah, Yes, I think what's happening is that base environment was already selected for the workspace. In which case it was auto activated.
If some other environment was pre selected, we would not be auto selecting and activating base in that case. Thanks for pointing it out!
Closing as expected in that case.
karrtikr
No branches or pull requests
Testing #20538
In the TPI's Case II & III, I notice that base gets activated anyways
The text was updated successfully, but these errors were encountered: