Devid

The bug with the parser may be resolved just by wrapping any exception raised by parser in a `ParseError`: ```patch --- a/rest_framework/request.py +++ b/rest_framework/request.py @@ -356,7 +356,7 @@ class Request:...

Could you provide a code sample of your model, serializer and data for checking?

The `value` field does not provide any [`default`](https://docs.djangoproject.com/en/5.0/ref/models/fields/#default), so it is expected to fail if no value for that field is provided. The real issue would be how did that...

> My guess is if you have only `null`, this counts as `default=None`? It is not documented nor in the codebase of django such behaviour for [null](https://docs.djangoproject.com/en/3.2/ref/models/fields/#null) or [default](https://docs.djangoproject.com/en/3.2/ref/models/fields/#default). Django...

If everyone here is having this issue when there are `UniqueConstraint`s this may be a side effect of #7438 because the constraint adds a `UniqueTogetherValidator` for given fields and thus...

> Another thing to note is that `ListField` already handles it properly (in #4118 ), in fact I'm just copying what's been done to `ListField` to `ListSerializer`. Since the use...

This is certainly be a breaking change with the current behaviour. However, IMHO, it is worth it for the sake of simplicity and uniformity. For the API user the `ListField`...

I have a similar error with [`django-push-notifications`](https://pypi.org/project/django-push-notifications/) ``` > [webserver compiler 7/7] RUN uv pip install -p /opt/venv/bin/python --compile --no-cache-dir -r /requirements.txt 'setuptools==71.1.0' --no-build-isolation: 3.430 × No solution found when...

Maybe the problem was related to `setuptools==72.0.0`, which was yanked.

This can be a problem when there are many users/groups. Because django is going to fetch every users and every groups each time the page is going to be rendered.