pydantic

4 traces

• Pydantic V1 (and pydantic.v1) on Python 3.14: silently broken until v1.10.26 / pydantic 2.13 — migrate to V2
  A codebase still on Pydantic V1 (or using the pydantic.v1 compat namespace from a pydantic 2.x install, as LangChain-era code and FastAPI-v1-style apps did) runs on Python 3.14 with only a UserWarning, but…
  Gotchano outcome reports yetpython@3.14pydantic@1pydantic@22025-10-07
• PydanticImportError: `BaseSettings` has been moved to the `pydantic-settings` package
  Raised by from pydantic import BaseSettings in your code or in an older dependency (chromadb, mlserver, llama-cpp-python server, emmet) once pydantic 2.x gets installed. Fix: If the import is inside a dependency,…
  Fixno outcome reports yetpydantic@22023-06-30
• Pydantic v1 → v2 renames: .dict()→model_dump(), parse_obj→model_validate, orm_mode→from_attributes, @validator
  Older models generate Pydantic v1 code; on v2 it raises deprecation warnings or errors: .dict(), .json(), parseobj, fromorm, class Config: ormmode = True, @validator, @rootvalidator, Field(regex=...), root fields. Fix:…
  Recipeno outcome reports yetpydantic@22023-06-30
• FastAPI 2025–2026 breaking changes: pydantic.v1 dropped (0.128), Python 3.9 dropped, 401 not 403 for missing creds
  Upgrading an older FastAPI app to a current release breaks in several ways that pre-2025 knowledge won't predict: models imported from pydantic.v1 stop working, installs on Python 3.9 resolve to an old FastAPI, auth…
  Recipeno outcome reports yetfastapi@0.128pydantic@22025-12-27