  should define the desired ``output_field``. For example, adding an
  ``IntegerField()`` and a ``FloatField()`` together should probably have
  ``output_field=FloatField()`` defined.
  
  The ``filter`` argument takes a :class:`Q object <django.db.models.Q>` that's
  used to filter the rows that are aggregated. See :ref:`conditional-aggregation`
  and :ref:`filtering-on-annotations` for example usage.
  
 
</s> remove .. class:: Aggregate(*expressions, output_field=None, filter=None, **extra)
 </s> add .. class:: Aggregate(*expressions, output_field=None, distinct=False, filter=None, **extra) </s> remove         super().__init__(*args, **kwargs)
 </s> add         super().__init__(*expressions, **extra)
The ``distinct`` argument determines whether or not the aggregate function
should be invoked for each distinct value of ``expressions`` (or set of
values, for multiple ``expressions``). The argument is only supported on
aggregates that have :attr:`~Aggregate.allow_distinct` set to ``True``.

  should define the desired ``output_field``. For example, adding an
  ``IntegerField()`` and a ``FloatField()`` together should probably have
  ``output_field=FloatField()`` defined.
  
The ``distinct`` argument determines whether or not the aggregate function
should be invoked for each distinct value of ``expressions`` (or set of
values, for multiple ``expressions``). The argument is only supported on
aggregates that have :attr:`~Aggregate.allow_distinct` set to ``True``.

  The ``filter`` argument takes a :class:`Q object <django.db.models.Q>` that's
  used to filter the rows that are aggregated. See :ref:`conditional-aggregation`
  and :ref:`filtering-on-annotations` for example usage.
  
keep keep keep add keep keep keep keep
 Fixed #28658 -- Added DISTINCT handling to the Aggregate class. 
docs/ref/models/expressions.txt