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.

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

In the latest version of VS2022, third-party libraries in Python cannot be intelligently completed #8111

Closed
vsfeedback opened this issue Dec 11, 2024 · 2 comments
Assignees

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[severity:I'm unable to use this version] [regression]
After VS2022 is updated to the latest version, create a new Python .py source file and save it to the .sln project. Then restart the computer, reopen the .sln project file, in the source code of the .py, all the third-party libraries can not be intelligently prompted, and cannot be intelligently completed. This issue only occurs after updating, restarting the system, and opening the old project, and the new project is not triggered
image.png


Original Comments

Feedback Bot on 12/3/2024, 05:20 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

@StellaHuang95
Copy link
Contributor

Thanks for reaching out! Could you provide the screenshot again? It appears to be corrupted. To help us investigate further, we’ll also need sample code and detailed repro steps.

When you say third-party libraries aren't being intelligently prompted, do you mean you’re not getting autocompletions? Have you ensured that the active Python environment is set to the one where those packages are installed?

Also, please set the Log Level to Trace under Tools -> Options -> Python -> Analysis, and check the Pylance output window. Let us know what the log says.

@TTORainyNight
Copy link

Resolved!
Sorry, I've been a bit busy lately and just saw the message. Thank you very much for your concern, after I upgraded to the latest update a few days ago, version number 17.12.3, this issue to be fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants