MyPy Static Type Checking

[CulmoneY]

Proposed Changes

This PR integrates MYPY static type checking into a Custom PYTA Checker. The following error types have been added:

• incompatible-argument-type
  Used when a function argument has an incompatible type.

• incompatible-assignment
  Used when there is an incompatible assignment.

• list-item-type-mismatch
  Used when a list item has an incompatible type.

• unsupported-operand-types
  Used when an operation is attempted between incompatible types.

• union-attr-error
  Used when accessing an attribute that may not exist on a Union type.

• dict-item-type-mismatch
  Used when a dictionary entry has an incompatible key or value type.

...

)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)	X
🐛 Bug fix (non-breaking change that fixes an issue)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📚 Documentation update (change that only updates documentation)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• I have updated the project Changelog (this is required for all changes).
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have verified that the pre-commit.ci checks have passed.
• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[coveralls]

Pull Request Test Coverage Report for Build 12637537577

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 46 of 47 (97.87%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.6%) to 92.509%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
python_ta/checkers/static_type_checker.py	34	35	97.14%

Totals
Change from base Build 12576220818:	0.6%
Covered Lines:	3211
Relevant Lines:	3471

---

💛 - Coveralls