Bump mypy from 1.20.2 to 2.0.0

[dependabot]

Bumps mypy from 1.20.2 to 2.0.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Mypy 2.1

We’ve just uploaded mypy 2.1.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

librt.vecs: Fast Growable Array Type for Mypyc

The new librt.vecs module provides an efficient growable array type vec that is optimized for mypyc use. It provides fast, packed arrays with integer and floating point value types, which can be several times faster than list, and tens of times faster than array.array in code compiled using mypyc. It also supports nested vec objects and non-value-type items, such as vec[vec[str]].

Refer to the documentation for the details.

Contributed by Jukka Lehtosalo.

librt.random: Fast Pseudo-Random Number Generation

The new librt.random module provides fast pseudo-random number generation that is optimized for code compiled using mypyc. It can be 3x to 10x faster than the stdlib random module in compiled code.

Refer to the documentation for the details.

Contributed by Jukka Lehtosalo (PR 21433).

Mypyc Improvements

• Make compilation order with multiple files consistent (Piotr Sawicki, PR 21419)
• Fix crash on accessing StopAsyncIteration (Piotr Sawicki, PR 21406)
• Fix incremental compilation with separate flag (Vaggelis Danias, PR 21299)

Fixes to Crashes

• Fix crash on partial type with --allow-redefinition and global declaration (Jukka Lehtosalo, PR 21428)
• Fix broken awaitable generator patching (Ivan Levkivskyi, PR 21435)

Changes to Messages

... (truncated)

Commits

• 7a76500 Remove +dev from version
• 5a3ab3b Changelog for mypy 2.0 (#21422)
• f9c86e2 Some changelog updates for 2.0 (#21413)
• 519eaf1 Bump librt to 0.10.0 (#21415)
• 158a620 Fix negative narrowing for containers (#21411)
• e556eb9 Try fixing mypy mypyc wheels (#21392)
• f2c9797 Expose --num-workers and --native-parser (#21387)
• db0cb2f Bump ast-serialize cache version (#21388)
• 1090ca6 Bump ast-serialize version to 0.3.0 only (#21391)
• 714ca9f [mypyc] Add note about librt.strings thread safety (#21383)
• Additional commits viewable in compare view

[github-actions]

🤖 Claude Code Review

Code Review: mypy 1.20.2 → 2.0.0 Version Bump

Code Quality

• ✅ Style guide: Single-line change in pyproject.toml — nothing to evaluate.
• ✅ No commented-out code: N/A.
• ✅ Meaningful variable names: N/A.
• ✅ DRY principle: N/A.
• ✅ Defects: No logic, no bugs possible in a version pin change. mypy 2.0.0 is a major version bump — this may introduce new type-checking strictness or breaking behavior, but that's expected and intentional for a dependency update.
• ✅ CLAUDE.md: No project-config concerns introduced.

Testing

• ✅ Unit/integration tests: Not applicable to a dependency version bump.
• ⚠️ Edge cases: mypy 2.0.0 is a major version release. Major releases of mypy historically introduce new default checks that can surface previously hidden type errors. The CI/lint pipeline should be verified to pass cleanly before merging (make lint / make mypy). If the CI passed, this is fine; if not reviewed post-lint, there is risk of hidden type regressions being masked.

Documentation

• ✅ README/API docs: No documentation changes needed for a dev-dependency bump.
• ⚠️ CHANGELOG.md: No CHANGELOG entry. Whether this is required depends on project policy; many projects omit changelog entries for dev-tooling bumps, but it's worth confirming.
• ✅ Markdown formatting: No markdown changes.

Security

• ✅ No hardcoded credentials: N/A.
• ✅ No license files: N/A.
• ✅ Input validation / error handling / sensitive data: N/A.

---

Summary

This is a straightforward dev-dependency bump. The only notable concern is that mypy 2.0.0 is a major version release — confirm that make mypy (or the full lint pipeline) passes cleanly against the existing codebase before merging, as major mypy releases can introduce new errors in previously-passing code. If CI is green, this change is safe to merge.

Automated code review analyzing defects and coding standards

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
src/senzing
szengineflags.py
szerror.py
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

🤖 Claude Code Review

Code Review

PR Summary: Bumps mypy from 1.20.2 to 2.0.0 in pyproject.toml.

---

Code Quality

• ✅ Style guide: Single-line change in a TOML config file; no style concerns.
• ✅ No commented-out code: N/A.
• ✅ Meaningful variable names: N/A.
• ✅ DRY principle: N/A.
• ✅ Defects: No logic errors. This is a major version bump (1.x → 2.0.0). mypy 2.0 dropped support for Python 3.8 and introduced several breaking changes in strict mode behavior. If the project targets Python 3.8, this could be an incompatibility — but since the project already uses mypy --strict (per CLAUDE.md), the CI lint run will surface any newly enforced errors quickly.
• ✅ CLAUDE.md: No issues; the config file is appropriately general.

Testing

• ✅ Unit/integration tests: Not applicable for a dependency version bump.
• ✅ Coverage: Not applicable.

Documentation

• ✅ README: No update needed.
• ✅ API docs: No update needed.
• ✅ Inline comments: No update needed.
• ✅ CHANGELOG.md: Dependency bumps of this kind are typically handled via automated PRs (Dependabot/Renovate) and do not require a CHANGELOG entry — consistent with the other recent bump commits in the repo history.
• ✅ Markdown formatting: No Markdown changes.

Security

• ✅ No hardcoded credentials: N/A.
• ✅ Input validation: N/A.
• ✅ Error handling: N/A.
• ✅ No sensitive data in logs: N/A.
• ✅ License files: None present.

---

Verdict: Approved. This is a routine dependency bump. The only thing worth confirming is that make lint passes cleanly after the upgrade, since mypy 2.0 is a major release that can surface new type errors under --strict. If CI is green, this is safe to merge.

Automated code review analyzing defects and coding standards