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

Unusual autocompletion behaviour in docstrings #16370

Closed
foo404 opened this issue Jan 10, 2025 · 3 comments
Closed

Unusual autocompletion behaviour in docstrings #16370

foo404 opened this issue Jan 10, 2025 · 3 comments
Assignees

Comments

@foo404
Copy link

foo404 commented Jan 10, 2025

Type: Bug

Behaviour

Recently, I noticed an unusual autocompletion bug. For illustration, I’m attaching a video that demonstrates the issue: typing test. and selecting test.py results in the docstring retaining test.test.py instead of just test.py. Could this be addressed, or is there a workaround?

test.mp4

Extension version: 2024.22.2
VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19041

@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Jan 10, 2025
@rchiodo
Copy link
Contributor

rchiodo commented Jan 10, 2025

Thanks for the issue but I can't reproduce the problem. I'm guessing you're running a notebook and this is happening after you start the kernel?

That works for me, but try updating your jupyter extension to the latest prerelease version. The jupyter kernel is providing that completion item and you may have an older jupyter extension.

@rchiodo rchiodo transferred this issue from microsoft/pylance-release Jan 10, 2025
@foo404
Copy link
Author

foo404 commented Jan 12, 2025

I think updating to the latest pre-release versions of the Python-related extensions resolved the issue. It no longer suggests available files such as test.py in the docstring. Also, this is a regular Python script, not a notebook.

vs-code.mp4

@DonJayamanne
Copy link
Contributor

think updating to the latest pre-release versions of the Python-related extensions resolved the issue.

Closing as fixed

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

No branches or pull requests

3 participants