10000 Should we add `py.typed` marker? · Issue #640 · python-lsp/python-lsp-server · GitHub
[go: up one dir, main page]
Skip to content

Should we add py.typed marker? #640

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
Closed
krassowski opened this issue May 10, 2025 · 0 comments · Fixed by #641
Closed

Should we add py.typed marker? #640

krassowski opened this issue May 10, 2025 · 0 comments · Fixed by #641
Labels
task
Milestone
v1.12.3

Comments

@krassowski
Copy link
Member

Currently plugins cannot take full advantage of mypy because pylsp is missing py.typed marker, even though it does make a decent use of typing.

error: Skipping analyzing "pylsp": module is installed, but missing library stubs or py.typed marker  [import-untyped]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
task
Projects
None yet
Milestone
v1.12.3
Development

Successfully merging a pull request may close this issue.

Add py.typed marker to pylsp imports to be analysed with mypy krassowski/python-lsp-server
2 participants
@ccordoba12 @krassowski
0