That seems like a reasonable thought. Though a BooleanField doesn't really
"support" microseconds, in that it doesn't support datetimes... But that's
the user's responsibility at that point.
On May 8, 2014 11:28 PM, "Claude Paroz" <notifications@github.com> wrote:

> In django/forms/forms.py:
>
> > @@ -590,6 +591,12 @@ def value(self):
> >              data = self.form.initial.get(self.name, self.field.initial)
> >              if callable(data):
> >                  data = data()
> > +                # If this is an auto-generated default date, nix the
> > +                # microseconds for standardized handling. See #22502.
> > +                if ((isinstance(data, datetime.datetime) or
> > +                        isinstance(data, datetime.time)) and
> > +                        not getattr(self.field.widget, 'supports_microseconds', False)):
>
> Now I wonder if the False default is right. Imagine someone uses a plain
> TextInput, does it not support microseconds? What's your opinion?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/django/django/pull/2638/files#r12465491>
> .
>