Django-typed-models

Fields defined in typed subclasses no longer get `null=True` added silently.

* If the field has a default value, we will use the default value instead of `None` for other types. You may need to either add `null=True` yourself, or create a migration for your app.
* If the field doesn't have a default value, a warning is logged and the `null=True` is added implicitly. This will be removed in typedmodels 0.9.

This release removes some magic around manager setup. Managers are now inherited using the normal Django mechanism.

If you are using a custom default manager on a TypedModel subclass, you need to make sure it is a subclass
of TypedModelManager. Otherwise type filtering will not work as expected.

This import path no longer works, as recent Django changes make it impossible:


from typedmodels import TypedModel


Instead, use:


from typedmodels.models import TypedModel