Skip to content

More strictness in mypy (WIP)#61

Open
prophile wants to merge 10 commits into
masterfrom
mypy-strictness
Open

More strictness in mypy (WIP)#61
prophile wants to merge 10 commits into
masterfrom
mypy-strictness

Conversation

@prophile

Copy link
Copy Markdown
Contributor

No description provided.

@prophile prophile requested review from PeterJCLaw and removed request for PeterJCLaw April 25, 2018 14:40
Comment thread setup.cfg
[mypy]
ignore_missing_imports=true
strict_optional=true
disallow_any_generics=true

@mthpower mthpower Apr 25, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is an example of what this would disallow? (the documentation isn't very clear on this)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

foo: List rather than foo: List[int]

@PeterJCLaw

Copy link
Copy Markdown
Contributor

👍

@coveralls

coveralls commented May 19, 2018

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.0001%) to 99.954% when pulling 49c12ef on mypy-strictness into 507f3d7 on master.

@danpalmer

Copy link
Copy Markdown
Contributor

@prophile I've fixed a few things here, but would appreciate a review as my approach might not be the best.

@prophile

Copy link
Copy Markdown
Contributor Author

I don't think we should bypass the layering tests for type checking. Actually I'd claim that the layering tests are correctly exposing dependencies here: where we're implicitly depending on the shape of component A from component B that's still a dependency on A from B even if it's previously not been unmasked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants