Pydantic V3 — 🙂 not 😱
A few people have asked me about Pydantic V3, mostly from the perspective of "what if Pydantic V3 breaks my stuff like V2 did?". I therefore want o describe what we think Pydantic V3 might look like. TL;DR: **V3 will not involve any large changes to the API as V2 did!** Instead V3 will: * remove the V1 migration helpers including [deprecated methods](https://github.com/pydantic/pydantic/blob/1e413857f48a807d3c81281b52c571f07c7077ee/pydantic/main.py#L1053-L1427), [migrations/redirect logic](https://github.com/pydantic/pydantic/blob/main/pydantic/_migration.py), and the [`pydantic.v1` shim](https://github.com/pydantic/pydantic/tree/main/pydantic/v1) * Fix some edge cases which we consider broken in V2 but don't want to change/fix for fear of breaking existing code, @sydney-runkle has done a great job of collecting these under the [`v3` label](https://github.com/pydantic/pydantic/issues?q=is%3Aopen+is%3Aissue+label%3Av3) - for example #9992 this is obviously incorrect, but doesn't affect many people (or it would have been reported earlier); still we don't want to change in a minor release * Potentially adopt some new logic which we have already [experimented with](https://docs.pydantic.dev/latest/version-policy/#experimental-features) in minor releases of V2, and are now confident won't change behavior for the vast vast majority of users, see #10032 for an example of this I would expect V3 will be released some time next year. The main point is we're endeavouring to move to
Posted by samuelcolvin on Aug 2, 2024, 11:41 AM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Pydantic V3 — 🙂 not 😱
A few people have asked me about Pydantic V3, mostly from the perspective of "what if Pydantic V3 breaks my stuff like V2 did?". I therefore want o describe what we think Pydantic V3 might look like. TL;DR: **V3 will not involve any large changes to the API as V2 did!** Instead V3 will: * remove the V1 migration helpers including [deprecated methods](https://github.com/pydantic/pydantic/blob/1e413857f48a807d3c81281b52c571f07c7077ee/pydantic/main.py#L1053-L1427), [migrations/redirect logic](https://github.com/pydantic/pydantic/blob/main/pydantic/_migration.py), and the [`pydantic.v1` shim](https://github.com/pydantic/pydantic/tree/main/pydantic/v1) * Fix some edge cases which we consider broken in V2 but don't want to change/fix for fear of breaking existing code, @sydney-runkle has done a great job of collecting these under the [`v3` label](https://github.com/pydantic/pydantic/issues?q=is%3Aopen+is%3Aissue+label%3Av3) - for example #9992 this is obviously incorrect, but doesn't affect many people (or it would have been reported earlier); still we don't want to change in a minor release * Potentially adopt some new logic which we have already [experimented with](https://docs.pydantic.dev/latest/version-policy/#experimental-features) in minor releases of V2, and are now confident won't change behavior for the vast vast majority of users, see #10032 for an example of this I would expect V3 will be released some time next year. The main point is we're endeavouring to move to
Comments (0)
No comments yet. Start the discussion.