The Wire · Showcase
FASTAPI AND PYDANTIC SHIFT TO UV FOR DOCS AND DEPENDENCIES
By RepoJournal · Filed · About FastAPI & Pydantic
3 people shipped this
FastAPI's documentation is standardizing on uv project templates, signaling a broader ecosystem shift toward Python's fastest-growing package manager.
FastAPI updated its documentation to use uv projects by default [1], replacing traditional venv-based examples across the docs. This mirrors a larger trend in the Python ecosystem where uv has become the preferred onboarding experience for new projects. The change affects how newcomers bootstrap FastAPI applications and sets expectations for the framework's community. Simultaneously, SQLModel's help documentation received updates [2], keeping auxiliary projects in sync with the main framework's direction. On the dependency front, Pydantic bumped Pillow to 12.3.0 [3], which removes non-image ImageCms modes as part of Pillow's ongoing cleanup. A UI layout fix landed in Pydantic's Skill component [4], addressing rendering issues in the framework's documentation tooling. All three major projects are moving in tandem: standardizing on modern tooling (uv), maintaining documentation quality, and keeping dependencies current.
One email a day. Unsubscribe in one click.
What actually shipped in FastAPI & Pydantic, written up every day — commits, pull requests, releases, and security advisories.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review FastAPI docs examples using your projects - uv is now the baseline fastapi/fastapi [plan]
- → Update internal onboarding docs to reference uv-based FastAPI setup fastapi/fastapi [plan]
- → Test Pydantic projects with Pillow 12.3.0 before next dependency update pydantic/pydantic [monitor]
References
- [1] 📝 Update docs to use uv projects by default ↗ fastapi/fastapi
- [2] 📝 Update help docs ↗ tiangolo/sqlmodel
- [3] Bump pillow from 12.2.0 to 12.3.0 ↗ pydantic/pydantic
- [4] Fix Skill layout ↗ pydantic/pydantic
