Django: Why does a migration pass a None value to a custom field in which I haven't set null=True?

Question

This is a custom field I defined to represent a time duration because I wanted a field that I could create with a single float type (seconds) and have that same value when I