NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #2753 most downloaded on PyPI
Type-Safe Pydantic Schemas for Django JSONFields
Latest stable
0.6.1
Last release 6 days ago
09 Nov 2026
Ships unpredictably
gaps range from 8 days to 8 months
Nearly every release is documented
notes for 54 of the last 60 stable releases
4 versions withdrawn
withdrawn after publishing
4 years old
75 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
I feel it's an overhead to define a full Config class in some cases, like: ```python class Config: json_encoders = ...
I feel it's an overhead to define a full Config class in some cases, like:
class Config:
json_encoders = ...
field: t.List[Schema] = SchemaField(config=Config)
The convenient solution is to pass a dict config instead:
field: t.List[Schema] = SchemaField(config={"json_encoders": ...})
Well, it is now possible to do so.
I'm considering current behavior with forward references resolution as expected. I.e. field schemas should be always defined before field declaration,
I'm considering current behavior with forward references resolution as expected. I.e. field schemas should be always defined before field declaration, otherwise it's not possible to bind a schema to the field during model initialzation. Note though, that annotation should still be declared as string/typing.ForwardRef, as long as prior constraint is satisfied. Main change: now such behavior is explicitly stated with tests.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
I tried to defer schema initialzation at a field descriptor level, but this approach did not succeeded with current migrations flow
I tried to defer schema initialzation at a field descriptor level, but this approach did not succeeded with current migrations flow
Nothing published for this version
Now, instead specifying explicit schema, one could write: ```py3 from django.db import Model from django_pydantic_field import SchemaField
Now, instead specifying explicit schema, one could write:
from django.db import Model
from django_pydantic_field import SchemaField
class MyModel(models.Model):
field: list[int] = SchemaField()
The schema will be inferred at model freezing step. Note that it's not possible to specify unresolved forward references at the moment.
In order to support this, I had to introduce a breaking changes in field api defintion: all Pydantic-prefixed classes should be used without this pref…
This is the first minor release of django-pydantic-field, with field-level type definitions:
class Foo(pydantic.BaseModel):
bar: int
class MyModel(models.Model):
meta: list[Foo] = SchemaField(schema=list[Foo])
In order to support this, I had to introduce a breaking changes in field api defintion:
all Pydantic-prefixed classes should be used without this prefix, e.g:
PydanticSchemaField -> SchemaField
PydanticSchemaRenderer -> SchemaRenderer
...
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.