-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add type checking #3
Comments
I thought I'd take a stab at this, posting this to make sure I'm on the right track.
yields
I'm making a branch that will deal with these errors. |
+1 to all of this, yeah. Those first four might not be because mypy can't find beancount but rather because it can't find type information about beancount. This might be because there is none. In that case, we could add type info to beancount (a big project, but a useful one, and they want the changes upstream) or we could add "#type: ignore" to the "import beancount" line. |
I have been making some progress on this, and you can take a look at my recent commits to see what this work looks like in practice. |
In an ideal world, a codebase that receives inconsistent attention would have a full suite of tests, type checks, and sample files. Tests are time-consuming to write and will have to wait on sample files anyway. But type checks! We can do those. This issue is for making progress on getting the codebase to pass "mypy --strict" and we can do it one bit at a time.
Along the way, that will prompt changes that hopefully get us to a better place with consistency and return values and classes.
The text was updated successfully, but these errors were encountered: