From bd8b075561b93f14ad4536f880749bd20dc40b8a Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Mon, 12 Aug 2024 21:14:39 -0700 Subject: [PATCH] update changelog, bump version --- docs/changelog.md | 17 +++++++++++++++++ pyproject.toml | 2 +- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/docs/changelog.md b/docs/changelog.md index 8a0a566..af19479 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -2,6 +2,23 @@ ## 1.* +### 1.3.1 - 24-08-12 - Allow arbitrary dtypes, pydantic models as dtypes + +Previously we would only allow dtypes if we knew for sure that there was some +python base type to generate a schema with. + +That seems overly restrictive, so relax the requirements to allow +any type to be a dtype. If there are problems with serialization (we assume there will) +or handling the object in a given array framework, we leave that up to the person +who declared the model to handle :). Let people break things and have fun! + +Also support the ability to use a pydantic model as the inner type, which works +as expected because pydantic already knows how to generate a schema from its own models. + +Only one substantial change, and that is a `get_object_dtype` method which +interfaces can override if there is some fancy way they have of getting +types/items from an object array. + ### 1.3.0 - 24-08-05 - Better string dtype handling API Changes: diff --git a/pyproject.toml b/pyproject.toml index 3a1ebf1..3f14e28 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "numpydantic" -version = "1.3.0" +version = "1.3.1" description = "Type and shape validation and serialization for numpy arrays in pydantic models" authors = [ {name = "sneakers-the-rat", email = "sneakers-the-rat@protonmail.com"},