Adding model_config = ConfigDict( protected_namespaces=()) to Base(BaseModel) class to resolve noisy pydantic warnings
Pydantic shows ~90 warnings like:
/Users/benieric/.pyenv/versions/3.10.14/envs/py3.10.14/lib/python3.10/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_quality_app_specification" has conflict with protected namespace "model_".
You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
warnings.warn(
This warning is raised when a pydantic model contains an attribute that is prefixed with "model_". Implementing workaround to suppress such warnings as they are noisy. Pydantic itself suggest You may be able to resolve this warning by settingmodel_config['protected_namespaces'] = ()` to resolve.
From pydantic docs: "While Pydantic will only emit a warning when an item is in a protected namespace but does not actually have a collision, an error is raised if there is an actual collision with an existing attribute:"
Error will still be emitted if an actual collision occurs
Issue #, if available:
Description of changes:
model_config = ConfigDict( protected_namespaces=())toBase(BaseModel)class to resolve noisy pydantic warningsPydantic shows ~90 warnings like:
This warning is raised when a pydantic model contains an attribute that is prefixed with "model_". Implementing workaround to suppress such warnings as they are noisy. Pydantic itself suggest
You may be able to resolve this warning by settingmodel_config['protected_namespaces'] = ()` to resolve.From pydantic docs: "While Pydantic will only emit a warning when an item is in a protected namespace but does not actually have a collision, an error is raised if there is an actual collision with an existing attribute:"
Reference:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.