python-types-contracts

To enforce explicit typing contracts for Python public interfaces, define clear module and package boundary rules. This reduces ambiguity and prevents unwarranted exposure of internal implementation details across your API surface.

Use pydantic for boundary validation at trust boundaries where external data enters your system. For internal code, apply plain types to prevent pydantic models from proliferating beyond their necessary validation scope.

Migrating Python API contracts requires migration-aware changes and clear boundary rules. Establish a concrete migration plan for changes to ensure backward compatibility while evolving your public API surface safely.

To stop pydantic models from proliferating beyond trust boundaries, enforce explicit boundary rules. Apply pydantic strictly at external trust perimeters and use plain types for internal code interactions.

Overusing Any or object across Python modules causes API drift by removing explicit typing constraints. Defining explicit public interface contracts replaces ambiguous types with clear boundary definitions to stabilize your API.

You do not need pydantic for internal Python typing contracts. Use plain types internally to structure code, reserving pydantic specifically for external trust boundaries where strict data validation is required.