-
Notifications
You must be signed in to change notification settings - Fork 130
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
Find a type checker and run it with Travis #379
Comments
another option: https://github.com/Microsoft/pyright |
@sjathin Yes, sure. Go ahead! |
Hi @priyanshunayan, I do have the latest revision, I am facing this issue. |
From your logs I can see that you are not inside the virtual environment. Indeed, the documentation is missing this step. I will make sure this gets added in the docs. In meantime please follow following steps before pip install:
/cc @sjathin |
Hello folks, I have an interesting opinion about this issue, how about we add a static analyzer such as DeepSource to the CI? These might be some interesting findings. |
@DARKPROGRAMMER16 you are using the dev branch or the master? coz the issue in dev branch is resolved |
I am in dev branch |
this content is not related to this issue. For any question, first use Slack and search for past issues or Google. If there is no other reference, open a new issue. Please follow Code Contribution rules. |
I'm submitting a
Current Behaviour:
Type annotations with
mypy
allow the code to tell developers which type of inputs/outputs are expected but there is no tool that checks that the annotations are respected by the functionsExpected Behaviour:
Some command-line tool should run with CI to check if types annotations are correct. See pyre
The text was updated successfully, but these errors were encountered: