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
In the picture above I used the interpreter selection to swap from a 3.7 64-bit interpreter to a 3.7.1 32-bit interpreter. The switch happened, but no new sys info was printed.
Could be related to my changes to not tie the server to the history window directly.
The text was updated successfully, but these errors were encountered:
…ng start of jupyter server (#4673)
For #4588
<!--
If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.:
- [x] ~Has unit tests & system/integration tests~
-->
- [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
- [x] Title summarizes what is changing
- [x] Has a [news entry](https://github.com/Microsoft/vscode-python/tree/master/news) file (remember to thank yourself!)
- [x] Has sufficient logging.
- [ ] Has telemetry for enhancements.
- [x] Unit tests & system/integration tests are added/updated
- [ ] [Test plan](https://github.com/Microsoft/vscode-python/blob/master/.github/test_plan.md) is updated as appropriate
- [ ] [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package-lock.json) has been regenerated by running `npm install` (if dependencies have changed)
- [ ] The wiki is updated with any design decisions/details.
In the picture above I used the interpreter selection to swap from a 3.7 64-bit interpreter to a 3.7.1 32-bit interpreter. The switch happened, but no new sys info was printed.
Could be related to my changes to not tie the server to the history window directly.
The text was updated successfully, but these errors were encountered: