Skip to content
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

Pylance extension details displayed in VS Code are out of date #3626

Closed
debonte opened this issue Nov 14, 2022 · 1 comment
Closed

Pylance extension details displayed in VS Code are out of date #3626

debonte opened this issue Nov 14, 2022 · 1 comment
Assignees
@debonte
Labels
fixed in next version (main) A fix has been implemented and will appear in an upcoming version

Comments

@debonte
Copy link
Contributor

debonte commented Nov 14, 2022

Environment data

  • Language Server version: 2022.11.21

Repro Steps

  1. Open extensions pane in VS Code
  2. Find and select Pylance
  3. In the Details tab of the newly opened "Extension: Pylance" window, look for the python.analysis.autoImportCompletions config setting

Expected behavior

The info states that the default value of python.analysis.autoImportCompletions is false.

Actual behavior

The info states that the default value of python.analysis.autoImportCompletions is true.
@debonte debonte self-assigned this Nov 14, 2022
@debonte debonte added fixed in next version (main) A fix has been implemented and will appear in an upcoming version and removed triage-needed labels Nov 14, 2022
@rchiodo rchiodo closed this as completed Nov 17, 2022
@rchiodo
Copy link
Contributor

rchiodo commented Nov 17, 2022

This issue has been fixed in prerelease version 2022.11.31, which we've just released. You can find the changelog here: CHANGELOG.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@debonte debonte

Labels
fixed in next version (main) A fix has been implemented and will appear in an upcoming version
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@debonte @rchiodo