modern-python

Enforce modern Python 3.14+ idioms by running modernization gates that eliminate legacy patterns, ensuring zero Union/Optional usage, built-in generics, PEP 695 type parameters, and @override decorators on overrides.

When migrating to Python 3.14, replace legacy typing patterns by removing from __future__ annotations, eliminating Union/Optional usage, adopting built-in generics, and defining type aliases with the type statement.

Use PEP 695 type parameters and the type statement to define modern Python 3.14+ type aliases and generics natively, eliminating the need for legacy Optional and Union imports in your data modeling workflows.

Yes, you can use this modernization checklist for large codebase migrations to guide teams through phased gates, reducing technical debt when upgrading from older Python versions to 3.14+ idioms.

Yes, refactoring to Python 3.14+ idioms requires removing from __future__ annotations, as the gate requirements mandate their removal alongside enforcing built-in generics and PEP 695 type parameters.

The best way to review Python code for legacy typing patterns is applying a repeatable modernization checklist that flags missing @override decorators and outdated Union/Optional usage during development.