$ the-wire · showcase
Pydantic docs examples stop passing silently, debug Python target lands in CI
By RepoJournal · Filed · About FastAPI & Pydantic · Composed from the cited sources · methodology
1 person shipped this
A quiet day in pydantic: documentation examples that were never actually raising now fail correctly, an unused error code is gone, and CI gains a debug Python test target.
Fix documentation examples not raising and remove unused `string_sub_type` unused error code pydantic/pydantic
Documentation examples that should have raised were not raising at all, so they passed regardless of what the library did; the examples now assert correctly, and the unused `string_sub_type` error code is removed. The root cause is upstream in pytest-examples, tracked in pydantic/pytest-examples, with the pydantic-side issue fixed by this change.
Add a debug Python test target in CI (#13820) pydantic/pydantic
A debug Python test target now runs in pydantic CI, the follow-up to the issue tracked in pydantic/pydantic. It exists so the test suite can be exercised against a debug build of the interpreter rather than only release CPython.
Add regression test for union member strictness on an enum type (#13815) pydantic/pydantic
by Louis Deconinck
A regression test pins the expected behavior for strictness of union members when one member is an enum type, so a future change to union validation fails loudly instead of quietly.
Add a debug Python test target in CI pydantic/pydantic
The same debug test target arrives as a pull request in pydantic/pydantic, opening the discussion on the approach before it lands.
Fix documentation examples not raising and remove unused `string_sub_type` unused error code (#13821) pydantic/pydantic
The commit carrying the documentation fix and the `string_sub_type` removal is merged to main, so the corrected examples and the smaller error-code surface are available to anyone tracking the default branch.
