Pydantic package organization episode 2: "The mess unfolds" by vcschapp · Pull Request #400 · OvertureMaps/schema

Victor Schappert (vcschapp) · 2025-10-09T00:22:27Z

tl;dr

This is part #2. Part #3 should drop by Friday 8/10 latest. I'm now expecting 5 total parts.

Squash Message

Re-org. Pydantic packages (2/N)

The destination is as described in PR #397 (1/N) and PR #400. In this
commit, the following value is added:

1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation
   destinations. The bug was discovered while refactoring the `mixin`
   module and the fix is reflected in the updated transportation schema
   baseline.
2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success)
   even if it found doctest failures. This bug was added in #397 when
   the `doctest` target was added and is now fixed.
3. Apply multiple suggestions from PR #397 including renaming
   `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary
   attribute from `PatternConstraint`.
4. Rename the sources package to annex in alignment as shown in the
   destination package diagram.
5. Begin refactoring `mixin` module to fix some known issues and polish
   it for final release. Changes made here:
      - Underlying implementation is replaced with the Pydantic function
        `create_model` (as was done in the scoping POC) which eliminates
        the need for `ConstrainedBaseModel` and should also eliminate
        MRO issues.
      - Underlying implementation uses some basic "JSON Schema algebra"
        to ensure that multiple decorators can coexist without breaking
        each others' JSON Schema changes.
      - The module name `mixin` is replaced by `model_constraint`, which
        feels more use case-oriented.
      - Initially one main decorator is migrated from `mixin` in the
        validation package to `model_constraint` in the system package.
        The rest will come next PR.
6. Migrate much of the validation package `README.md` into the system
   package's main module `__init__.py` and migrate the examples into
   doctests.
7. Re-home a few other bits of functionality from validation to core.
8. Bring the https://github.com/vcschapp/overture-schema-pydantic
   scoping into core as `scoping.py` and fix up the linter errors. This
   is not wired up yet, but that's Coming Soon, likely in episode 4.

Stay tuned for episode 3, where we will finish re-homing the validation
package.

Journey

Part 1 is in PR Pydantic package organization episode 1: "Making huge mess" #397.

Destination

Packages.
- ▶️ The package setup will be organized as diagrammed below.
- ⬜️ Package dependencies and pyproject.toml will be standardized.
Documentation.
- ✅ All doctests will pass and automatically be enforced to pass by make check.
- ▶️ All documentation will pass pydocstyle with the NumPy convention. (As of now, the tool reports too many complaints to add it into make check.)
- ⬜️ pydocstyle will be enforced by make check.
- ⬜️ docformatter will be run by make check.
- ▶️ Package-level README content will migrate into the package's __init__.py docstring.
- ⬜️ There will be a doc target in the Makefile that does uv run pdoc to a useful place.
- ⬜️ Our most foundational BaseModel base class in system will be given an optional description property that can be used to provide class-level documentation for the schema user persona. (See this conversation in the comments on this PR.) I no longer think this is necessary as there's an evolving clean separation between fields and models (user-facing descriptions or docstrings) and system types (builder-facing docstrings).
Modules.
- ▶️ Re-exports will be standardized and everything of value will be re-exported into the main module.
- ⬜️ In theme packages, the primary module will be feature, which will contain the feature models and the main simple types that support them.
- ⬜️ In theme packages, if a field contains a theme-specific "deep model" then it will be given its own module, e.g. perspectives.

Packaging Deep Dive

Recapping the target package organization from part 1 (PR #397):

…...` and move to system

#397

…doctests

…tensionPrefixModelConstraint wasn't used anywhere

…overture-schema-pydantic/blob/main/src/overture_schema_pydantic/scoping.py

…es so make check passes Now I want to turn back to mixin/model constraints and implement require_field_from().

…e model_constraint

…destinations The "require one of" for destinations wasn't reflected in the JSON schema, fixed now: https://github.com/OvertureMaps/schema/blob/dev/schema/transportation/segment.yaml#L104-L106

-#397 (comment)

…tring slightly

Seth Fitzsimmons (sethfitz) · 2025-10-13T03:48:01Z



-class Address(StrictBaseModel):
+# TODO - vic - move this into Places


👍

FWIW, it's only here because this matches where it was located in the JSON Schema.

Seth Fitzsimmons (sethfitz) · 2025-10-13T03:50:08Z

+def allow_extension_fields() -> Callable:
+    """Decorator to allow only ext_* prefixed extension fields."""
+
+    def decorator(cls: type[BaseModel]) -> type[BaseModel]:
+        constraint = ExtensionPrefixValidator()
+        register_constraint(cls, constraint)
+        return cls
+
+    return decorator


Seth Fitzsimmons (sethfitz) · 2025-10-13T03:53:08Z

@@ -0,0 +1,208 @@
+from collections.abc import (


Should I come back and review this once it's wired up? I haven't spent the time to properly grok it, but I suspect that I have questions that are better answered by comments, how it's used by models.

Seth Fitzsimmons (sethfitz) · 2025-10-13T04:36:19Z

+    no_extra_fields,
+)
+
+sys.path.insert(0, str(Path(__file__).parent))  # Needed to import `util` peer module.


This may be fixable within pyproject.toml, setting up tests/ to behave as modules... Did you try anything else?

No. I took the lazy man's way out. (Well lazy and time-constrained.)

We should fix it for sure. But being a test I'm thinking it's a bit farther down for now.

Seth Fitzsimmons (sethfitz) · 2025-10-13T04:39:20Z


 if __name__ == "__main__":
    pytest.main([__file__])


Whoops. This is probably extraneous too.

…ing.py Apply Seth's suggestion on color docs consistency. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

…nit__.py Apply Seth's suggestion on grammar correction. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

Apply Seth's suggestion on confidence score precision. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

Re-org. Pydantic packages (2/N) The destination is as described in PR #397 (1/N) and PR #400. In this commit, the following value is added: 1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation destinations. The bug was discovered while refactoring the `mixin` module and the fix is reflected in the updated transportation schema baseline. 2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success) even if it found doctest failures. This bug was added in #397 when the `doctest` target was added and is now fixed. 3. Apply multiple suggestions from PR #397 including renaming `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary attribute from `PatternConstraint`. 4. Rename the sources package to annex in alignment as shown in the destination package diagram. 5. Begin refactoring `mixin` module to fix some known issues and polish it for final release. Changes made here: - Underlying implementation is replaced with the Pydantic function `create_model` (as was done in the scoping POC) which eliminates the need for `ConstrainedBaseModel` and should also eliminate MRO issues. - Underlying implementation uses some basic "JSON Schema algebra" to ensure that multiple decorators can coexist without breaking each others' JSON Schema changes. - The module name `mixin` is replaced by `model_constraint`, which feels more use case-oriented. - Initially one main decorator is migrated from `mixin` in the validation package to `model_constraint` in the system package. The rest will come next PR. 6. Migrate much of the validation package `README.md` into the system package's main module `__init__.py` and migrate the examples into doctests. 7. Re-home a few other bits of functionality from validation to core. 8. Bring the https://github.com/vcschapp/overture-schema-pydantic scoping into core as `scoping.py` and fix up the linter errors. This is not wired up yet, but that's Coming Soon, likely in episode 4. 9. At Seth's suggestion, switch `ConfidenceScore` from `float64` to `float32` though we will have to double-check the actual value in the Parquet model here. Stay tuned for episode 3, where we will finish re-homing the validation package.

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

Re-org. Pydantic packages (2/N) The destination is as described in PR #397 (1/N) and PR #400. In this commit, the following value is added: 1. 🐞 Fix bug: The `@any_of` decorator was not working with transporation destinations. The bug was discovered while refactoring the `mixin` module and the fix is reflected in the updated transportation schema baseline. 2. 🐞 Fix bug: The `make doctest` target exited with code 0 (success) even if it found doctest failures. This bug was added in #397 when the `doctest` target was added and is now fixed. 3. Apply multiple suggestions from PR #397 including renaming `CountryCode` to `CountryCodeAlpha2` and dropping an unnecessary attribute from `PatternConstraint`. 4. Rename the sources package to annex in alignment as shown in the destination package diagram. 5. Begin refactoring `mixin` module to fix some known issues and polish it for final release. Changes made here: - Underlying implementation is replaced with the Pydantic function `create_model` (as was done in the scoping POC) which eliminates the need for `ConstrainedBaseModel` and should also eliminate MRO issues. - Underlying implementation uses some basic "JSON Schema algebra" to ensure that multiple decorators can coexist without breaking each others' JSON Schema changes. - The module name `mixin` is replaced by `model_constraint`, which feels more use case-oriented. - Initially one main decorator is migrated from `mixin` in the validation package to `model_constraint` in the system package. The rest will come next PR. 6. Migrate much of the validation package `README.md` into the system package's main module `__init__.py` and migrate the examples into doctests. 7. Re-home a few other bits of functionality from validation to core. 8. Bring the https://github.com/vcschapp/overture-schema-pydantic scoping into core as `scoping.py` and fix up the linter errors. This is not wired up yet, but that's Coming Soon, likely in episode 4. 9. At Seth's suggestion, switch `ConfidenceScore` from `float64` to `float32` though we will have to double-check the actual value in the Parquet model here. Stay tuned for episode 3, where we will finish re-homing the validation package.

The destination is as described in PR #397 (1/N), PR #400, and PR #403. In this commit, the following value is added: 1. 🐞 Fix bug: The `not_required_if` mixin wasn't meeting the original schema intent, which result in the `DivisionBoundary` feature type having the wrong JSON Schema. The expected behavior is "if the boundary is at the country level, then the `country` pair should be omitted" but instead it did two variations: in the Python validator, it required the country pair to be present; and in the JSON Schema, it required the country pair to be present, but only if the condition was not true. Both were subtly wrong. The bug is fixed in this commit and the mixin is renamed to `forbid_if`, which I hope will make the semantics more obvious. 2. 🐞 Fix bug: Very subtle, but the mixin model constraint validators did not work correctly if added directly to a `Feature` model, because they aren't aware of the quirky multi-tiered GeoJSON JSON Schema where most properties get pushed down into "properties", but some do not. This is (hopefully ... 🤞) fixed in the new `Feature` model in the system package. 3. 🐞 Fix bug: Very subtle, but the previous `Feature` model's JSON Schema did not prohibit fields named `"id"`, `"bbox"`, and `"geometry"` within the properties object. This created a weird quirk where in a poisoned JSON object containing those values under properties, the properties version would overwrite the root version. This is fixed by explicitly prohibiting those fields in the JSON Schema for the `Feature` class' properties object. 4. 🐞 Fix bug: The `ExtensibleBaseModel`'s `patternProperties` got put both at the top level of the GeoJSON Feature schema and in the "properties" object schema. This would have allowed the input JSON to contain `ext_*` at two levels, which doesn't meet the original schema intent. As part of this bug fix, `ExtensibleBaseModel` is collapsed directly into `OvertureFeature` and the `ext_*` feature is documented as being on a deprecation path. 5. The `validation` package is officially deleted as its essential George functions have all been re-homed either into `system` or `core`. 6. All model constraint mixins have been refactored along the lines started in PR #400. They are now called `@forbid_if`, `@min_fields_set`, `@no_extra_fields`, `@radio_group`, `@require_any_of`, and `@require_if`. 7. A type hint, `Omitable[T]` has been added to the system package. This type hint allows a Pydantic model to "naturally" get JSON Schema semantics for omitted values - it de-conflates optionality and nullability, which Pydantic currently conflates. In an upcoming episode, I hope to replace the `X | None` unions in the existing model with `Omitable[X]`. 8. The existing `Feature` class from the `core` package has been split into two: (i) `Feature` in the `system` package now acts as a generic feature and owns all the funky GeoJSON logic, allowing George enthusiasts to work with a nice ergonomic feature type without having to use an "Overture"-flavored feature; (ii) `OvertureFeature` in the `core` package adds the Overture schema specific flavoring on top of `Feature`. 9. The `ref` module from `core` has been pushed down into `system` and the dependency on `(Overture)Feature` has been factored out in favor of a generic dependency on an `Identified` model, which is basically just a `BaseModel` with a mandatory ID. Stay tuned for episode 4, where we will re-organize the core package.

Victor Schappert (vcschapp) added 20 commits October 3, 2025 15:08

wip: rename sources to annex

71be46d

wip: Rename CategoryPatternConstraint/PlaceCategory as `SnakeCase…

8512f06

…...` and move to system

wip: Rename CountryCode -> CountryCodeAlpha2 as discussed on PR #397

3010719

#397

wip - Start migrating "validation" README to "system" docstring with …

f06159e

…doctests

Fix bug: make doctest exits with code 0 even if a doctest fails 🐞

3ccd9f9

wip - Move LR constraint from validation into core

19ae61a

wip - Move ConfidenceScore constraint up into core

bdd8339

wip - Delete fully re-homed validation.constraint package - note Ex…

4365230

…tensionPrefixModelConstraint wasn't used anywhere

wip - Re-home the ext_ prefix stuff up into core

94d67d8

wip - [BROKEN] Paste in scoping POC from https://github.com/vcschapp/…

305a19f

…overture-schema-pydantic/blob/main/src/overture_schema_pydantic/scoping.py

wip - [PASSES] scoping - Fix all ruff/mypy formatting and typing issu…

ae785ab

…es so make check passes Now I want to turn back to mixin/model constraints and implement require_field_from().

wip - Rename constraint module -> field_constraint so mixin can becom…

f258d0b

…e model_constraint

wip - [BROKEN] checkpoint where mixin replacement POC ALMOST working

592708b

wip - [PASSING!] @require_one_of works and fixed existing bug with …

f5f6ed0

…destinations The "require one of" for destinations wasn't reflected in the JSON schema, fixed now: https://github.com/OvertureMaps/schema/blob/dev/schema/transportation/segment.yaml#L104-L106

wip - Simplify scoping sketch using new RequireAnyOfConstraint

1f563ab

wip - Remove old @any_of

45adac4

wip - Increase model_constraint module unit testing

879e636

wip - Fully migrate StrictBaseModel -> @no_extra_fields

548634f

wip - unit test @no_extra_fields

f22f6b1

wip - Apply comment from PR #397 (pattern)

2cf4b9b

-#397 (comment)

Victor Schappert (vcschapp) requested a review from Seth Fitzsimmons (sethfitz) October 9, 2025 00:22

Victor Schappert (vcschapp) temporarily deployed to staging October 9, 2025 00:22 — with GitHub Actions Inactive

wip - undo accidental changes to gers/ dir

fe9c7a6

Victor Schappert (vcschapp) temporarily deployed to staging October 9, 2025 00:37 — with GitHub Actions Inactive

Victor Schappert (vcschapp) mentioned this pull request Oct 9, 2025

Pydantic package organization episode 1: "Making huge mess" #397

Merged

wip - rename ModelConstraint.attach to .decorate and improve its docs…

a496288

…tring slightly

Victor Schappert (vcschapp) temporarily deployed to staging October 9, 2025 02:11 — with GitHub Actions Inactive

Victor Schappert (vcschapp) temporarily deployed to staging October 9, 2025 02:27 — with GitHub Actions Inactive

wip - more docs tweaks

735453f

Victor Schappert (vcschapp) temporarily deployed to staging October 9, 2025 02:49 — with GitHub Actions Inactive

Seth Fitzsimmons (sethfitz) reviewed Oct 13, 2025

View reviewed changes

Seth Fitzsimmons (sethfitz) approved these changes Oct 13, 2025

View reviewed changes

Update packages/overture-schema-system/src/overture/schema/system/str…

44ff5ae

…ing.py Apply Seth's suggestion on color docs consistency. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:27 — with GitHub Actions Inactive

Update packages/overture-schema-system/src/overture/schema/system/__i…

0bfae8f

…nit__.py Apply Seth's suggestion on grammar correction. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:28 — with GitHub Actions Inactive

Update packages/overture-schema-system/src/overture/schema/system/__i…

c6f8892

…nit__.py Apply Seth's suggestion on grammar correction. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:28 — with GitHub Actions Inactive

Update packages/overture-schema-core/src/overture/schema/core/types.py

9c32f38

Apply Seth's suggestion on confidence score precision. Co-authored-by: Seth Fitzsimmons <sethfitz@amazon.com>

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:28 — with GitHub Actions Inactive

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:31 — with GitHub Actions Inactive

wip - Finalize float32 change

86314a9

Victor Schappert (vcschapp) force-pushed the pp2 branch from 0c0f7f9 to 86314a9 Compare October 13, 2025 14:33

Victor Schappert (vcschapp) temporarily deployed to staging October 13, 2025 14:33 — with GitHub Actions Inactive

Victor Schappert (vcschapp) merged commit b59c59a into pydantic Oct 13, 2025
3 checks passed

Victor Schappert (vcschapp) deleted the pp2 branch October 13, 2025 14:38

Victor Schappert (vcschapp) mentioned this pull request Oct 16, 2025

Pydantic package organization episode 3: "System update complete" #403

Merged

Victor Schappert (vcschapp) mentioned this pull request Oct 28, 2025

Pydantic package organization episode 4: "Scope is in (scope)" #412

Merged

Victor Schappert (vcschapp) mentioned this pull request Nov 5, 2025

Pydantic package organization episode 5: "Only mostly dead" #415

Merged

Victor Schappert (vcschapp) mentioned this pull request Mar 12, 2026

[REFACTOR] Organize divisions theme Pydantic package, add missing relationships, tidy and add docs #469

Merged

Victor Schappert (vcschapp) mentioned this pull request Jul 24, 2026

[REFACTOR] Organize transportation theme Pydantic package, add relationships, sync JSON Schema, and tidy docs #598

Merged

Victor Schappert (vcschapp) mentioned this pull request Jul 31, 2026

[REFACTOR] Delete annex, fix last docformat issues, enable docformat check in make check #629

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Pydantic package organization episode 2: "The mess unfolds" - #400

Pydantic package organization episode 2: "The mess unfolds"#400
Victor Schappert (vcschapp) merged 30 commits into
pydanticfrom
pp2

Victor Schappert (vcschapp) commented Oct 9, 2025 •

edited

Loading

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Uh oh!

Victor Schappert (vcschapp) Oct 13, 2025

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants



		class Address(StrictBaseModel):
		# TODO - vic - move this into Places

Uh oh!

Conversation

Victor Schappert (vcschapp) commented Oct 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

tl;dr

Squash Message

Journey

Destination

Packaging Deep Dive

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Victor Schappert (vcschapp) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Seth Fitzsimmons (sethfitz) Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Victor Schappert (vcschapp) commented Oct 9, 2025 •

edited

Loading