You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
python: do not refresh interpreters on quickpick open (#4462)
<!-- Thank you for submitting a pull request.
If this is your first pull request you can find information about
contributing here:
* https://github.com/posit-dev/positron/blob/main/CONTRIBUTING.md
We recommend synchronizing your branch with the latest changes in the
main branch by either pulling or rebasing.
-->
<!--
Describe briefly what problem this pull request resolves, or what
new feature it introduces. Include screenshots of any new or altered
UI. Link to any GitHub issues but avoid "magic" keywords that will
automatically close the issue. If there are any details about your
approach that are unintuitive or you want to draw attention to, please
describe them here.
-->
related to #3944
Keeps the lists of interpreters the same, rather than refreshing only
the first time the Select Interpreter QuickPick is opened which makes it
seem like the Positron dropdown is out of sync.
This nudges people towards refreshing manually when they have created a
new environment, which I believe to be the desired behavior since
Positron will not have to continually watch for new envs (which can be
expensive, some discussion
#2003). I've opened #4269 to
track better UI to make refreshing interpreters more obvious.
### QA Notes
<!--
Add additional information for QA on how to validate the change,
paying special attention to the level of risk, adjacent areas that
could be affected by the change, and any important contextual
information not present in the linked issues.
-->
Scenario 1:
1. Open Positron
2. Create new pyenv environment via something like `pyenv virtualenv
3.9.4 test-startup`
3. Check: no new env discovered in Positron dropdown, no new env
discovered in `Python: Select Interpreter`
4. Refresh envs using button in `Python: Select Interpreter`
5. See env populate in both locations
Scenario 2:
1. Open Positron
2. Create new pyenv environment via something like `pyenv virtualenv
3.9.4 test-startup`
3. Close Positron
4. Open Positron
5. See env populate in both locations
Copy file name to clipboardExpand all lines: extensions/positron-python/src/client/interpreter/configuration/interpreterSelector/commands/setInterpreter.ts
+12-5Lines changed: 12 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -208,12 +208,19 @@ export class SetInterpreterCommand extends BaseInterpreterSelectorCommand implem
0 commit comments