Given how Pydantic 2 broke compatibility with Pydantic 1 in a way that's still shaking out - you can't use 2 in a project that has dependencies that use 1 without making changes to those dependencies...
... I wonder what the downsides of releasing Pydantic 2 as a new package called "pydantic2" such that it could be installed in the same namespace as the original pedantic would have been?
Presumably this is how Jinja ended up as "jinja2" forever?
Simon Willison /
npub13v…4w5eu
2024-01-09 18:11:15
Author Public Key
npub13v97j0kknscwnf5pt87nsn7cxzxwfwl3dsu7ss8qsq7ukmqgwg8q84w5euPublished at
2024-01-09 18:11:15Event JSON
{
"id": "545b45c27ea517686826fb915c3f8a2f5ee2d9f4703cbbdef12bc6eb6fb7efcf",
"pubkey": "8b0be93ed69c30e9a68159fd384fd8308ce4bbf16c39e840e0803dcb6c08720e",
"created_at": 1704823875,
"kind": 1,
"tags": [
[
"proxy",
"https://fedi.simonwillison.net/users/simon/statuses/111727337488809740",
"activitypub"
]
],
"content": "Given how Pydantic 2 broke compatibility with Pydantic 1 in a way that's still shaking out - you can't use 2 in a project that has dependencies that use 1 without making changes to those dependencies...\n\n... I wonder what the downsides of releasing Pydantic 2 as a new package called \"pydantic2\" such that it could be installed in the same namespace as the original pedantic would have been?\n\nPresumably this is how Jinja ended up as \"jinja2\" forever?",
"sig": "13c8fd96069ed2a78d164a8e3bf4c57731c98293bc9e332213cd254bcf1bc03d7bc5ce426fe6d2bec03623e80a9669613dce34b273bf01c93254551a009f45f9"
}