pydantic-basesettings-class-attributes

Pydantic BaseSettings throws a non-annotated attribute error because it treats un-annotated class attributes as model fields. You must explicitly annotate internal constants with ClassVar or move them to module scope to prevent model-field leakage.

Fix non-annotated attribute errors in Pydantic BaseModel subclasses by annotating internal mappings or flags with ClassVar. Alternatively, relocate hard-coded constants outside the class as module-level variables to ensure proper model validation.

Use ClassVar annotations in Pydantic models when defining internal mappings, flags, or hard-coded configurations as class attributes. This explicitly marks them as non-field attributes, preventing them from being processed as model fields during validation.

No, resolving non-annotated class attributes in Pydantic requires no external packages. It relies entirely on standard Python tooling and Pydantic type annotations, using built-in ClassVar typing or module-level variable extraction to fix validation errors.

The best way to refactor hard-coded mappings in Pydantic BaseSettings is to extract them as module-level constants or annotate them with ClassVar. This facilitates safer refactoring and avoids model-field leakage during class initialization.