Marti Raudsepp

I can't submit a PR because my "fix" (more like workaround) can only be applied in user code. 😄 Do you have any ideas why `CharField` and similar simple fields...

There is a lot of stuff. I have autogenerated the [relase notes for 1.13.0](https://github.com/typeddjango/django-stubs/releases/tag/1.13.0) now, I hope that's helpful. :) I guess it was by mistake that the release notes...

My understanding is that `fields` may be **omitted**. But that doesn't mean it can be set to `None`. Per DRF documentation ```python class AccountSerializer(serializers.ModelSerializer): class Meta: model = Account exclude...

Hi The plugin itself does not read the mypy configuration file. The plugin invokes the mypy command, and mypy exits with error code 2 in your situation. Please try running...

ngnpope said this should be fixed by #1050. Can this be closed now?

Cc: @sobolevn To get some feel about where the bugs are, I took the liberty of creating a few extra labels and going throug a bunch of most recent issues...

> Or how would you suppress this error? I usually add an `else:` block that raises an error: ```python elif request.method == "POST": return Response({}) else: raise AssertionError(f"Unhandled method {request.method}")...

Another alternative: I've been using djangorestframework-dataclasses and have been happy with it: https://github.com/oxan/djangorestframework-dataclasses Pydantic is probably a cleaner implementation without DRF's baggage, but DRF-dataclasses integrates better with Django REST Framework.

Django 4.0 is decently well supported by now. If there are omissions, please open specific issues describing what is wrong.

I'll close this for now. Feel free to reopen or reply if you're able to test and there are still issues.