[Alex3917]

> I also don't see anything wrong with explicit default arguments.

I think explicit default arguments should be used when they're documenting some behavior that the reader might not know or remember, but that isn't the case here.

E.g. with python's enumerate built-in, it's useful to the reader to know that it starts at 0 or whatever. But with Django's models, adding (null=False, blank=False, editable=True) isn't telling the reader anything that they likely wouldn't already know or assume, it's just making the code more difficult to read.

[japhyr]

Yes, I first read those as (null=True, blank=True) because I've never written out those arguments when their default is False. So for me writing them out explicitly with their defaults is an anti-pattern.