api.run has empty reports when crashing early

I'm seeing a case where CLI would ouput useful messages but api.run is not. This causes https://github.com/PyCQA/prospector to think that the mypy run was successful when it wasn't (granted, prospector should look at exit_status).

mypy.ini

[mypy]
plugins = mypy_django_plugin.main
warn_return_any = True
warn_unused_configs = True
disallow_subclassing_any = True
disallow_any_generics = True
disallow_untyped_calls = True
disallow_untyped_defs = True
disallow_incomplete_defs = True
check_untyped_defs = True
disallow_untyped_decorators = True
no_implicit_optional = True
warn_redundant_casts = True
warn_unused_ignores = True
mypy_path = stubs

[mypy.plugins.django-stubs]
django_settings_module = "imake.settings"

Output of CLI

env PYTHONPATH=(pwd) mypy core/shortcuts.py
oscar_forks/catalogue/models.py:6: error: Module 'oscar.apps.catalogue.abstract_models' has no attribute 'AbstractCategory'
oscar_forks/catalogue/models.py:21: error: Class cannot subclass 'AbstractCategory' (has type 'Any')
stubs/oscar/apps/catalogue/abstract_models.pyi:3: error: INTERNAL ERROR -- Please try using mypy master on Github:
https://mypy.rtfd.io/en/latest/common_issues.html#using-a-development-mypy-build
If this issue continues with mypy master, please report a bug at https://github.com/python/mypy/issues
version: 0.720
stubs/oscar/apps/catalogue/abstract_models.pyi:3: : note: please use --show-traceback to print a traceback when reporting a bug

Return value of api.run

('', '', 2)

Start at the api.run entry point and compare its behavior with the CLI using the provided mypy.ini configuration and mypy command. Reproduce the early crash, then verify that api.run exposes the same diagnostic output as the CLI while preserving the exit status.