Marti Raudsepp

Does the `strict_settings = false` option help in these use cases? See README: [How to use a custom library to handle Django settings?](https://github.com/typeddjango/django-stubs#how-to-use-a-custom-library-to-handle-django-settings) It was introduced in django-stubs 4.2.2 (https://github.com/typeddjango/django-stubs/pull/1557)

Thanks for confirming, I'll close this issue.

> Do we have a way to consistently reproduce this issue? Not that I know of. I could try to reduce this down to a minimal example if you're interested...

This was fixed in django-stubs 4.2.3.

There's an open PR #1241. I am not entirely sure why it stalled. There is a crash with mypy 0.991 when used with Django 3.2 (#1261), but IMO it shouldn't...

@djbrown django-stubs 1.13.1 released now: https://github.com/typeddjango/django-stubs/releases/tag/1.13.1

Just to explain why this wasn't implemented yet: I was considering changing the version scheme a few months ago (#1316), but I felt some apprehensive vibes in a few comments...

I believe this happens when using the `pretty = true` setting in mypy configuration, which turns on word wrapping: https://mypy.readthedocs.io/en/stable/config_file.html#confval-pretty There is an undocumented command line argument `--no-pretty` that the...

> it is in fact documented Ah nice! I only checked the online docs.

Ugh. Every Python type inherits from `object`, which provides the `__init__(self)` method. So basically every constructor with required arguments violates the Liskov substitution principle.