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

PR: Add mypy plugin to core plugins #838

Open
wants to merge 58 commits into
base: develop
Choose a base branch
from

Conversation

steff456
Copy link
Contributor

@steff456 steff456 commented Aug 3, 2020

This PR migrates the pyls-mypy plugin, https://github.com/tomv564/pyls-mypy, to the core plugins of PyLS for us to maintain

tomv564 and others added 30 commits August 8, 2017 15:06
Not 100% sure when this was introduced.
message contains now quotes in pyls 0.18.0
This provides slightly better context than just the single character
at that point.
…word

Highlight the word at the point Mypy flags it
Else we get all the errors for all the imported files on the current file.
Add '--follow-imports silent' to mypy invocation
singulared and others added 23 commits April 12, 2019 23:41
Seeing this with disallow_untyped_defs=True for example.
Test on Windows before releasing?
Fix diagnostics start position
Moved the metadata to setup.cfg
Install and use future only if python2
@ccordoba12
Copy link
Contributor

@uschi2000, I'm also having troubles in this repo to merge pull requests. As you can see, the Appveyor integration is required to pass, but its status is not registered by Github. That's very strange because tests are passing just fine on the Appyevor servers:

https://ci.appveyor.com/project/gatesn/python-language-server/builds/34455591

A possible solution for this would be to move to move testing to Github actions, as proposed by @goanpeca on PR #803.

@uschi2000
Copy link

So it seems that the appveyor integration is done in terms of @gatesn 's user name. Since he is no longer in the Palantir Org this integration probably broke.

@uschi2000
Copy link

@gatesn could you give me a hand in restoring/migrating/fixing the appveyor CI integration for this repo (and python-grpc)? Thanks very much!

@mpanarin
Copy link
Contributor

mpanarin commented Aug 4, 2020

@steff456 What is the issue with using the plugin? It does its job just fine.
I think it is worth to try finishing the #391 for mypy daemon integration, thus making the plugin and mypy api integration obsolete?

Mypy daemon works best for project setups, while the plugin only runs the checker on a single file, missing a lot of type checks coming from imports, etc. as mentioned in the tomv564/pyls-mypy#24

@gatesn
Copy link
Contributor

gatesn commented Aug 4, 2020

@uschi2000 not sure what I need to do here? Can you remove appveyor from required checks? I had a look and it says AppVeyor permissions are inherited from GitHub perms. So if you're an admin here you should get admin there.

@uschi2000
Copy link

@gatesn I personally have no idea what the appveyor integration does here and whether we need it or not ;)

@ccordoba12
Copy link
Contributor

I personally have no idea what the appveyor integration does here and whether we need it or not ;)

@uschi2000, thanks again for your help sorting out these issues.

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

Successfully merging this pull request may close these issues.

None yet