  
      This function can raise an exception if ``value`` doesn't exist or is
      ambiguous because of DST transitions.
  
  .. function:: make_naive(value, timezone)
  
      Returns an naive :class:`~datetime.datetime` that represents in
      ``timezone``  the same point in time as ``value``, ``value`` being an
      aware :class:`~datetime.datetime`
  
 
</s> remove     :class:`~datetime.datetime`.
 </s> add     :class:`~datetime.datetime`. If ``timezone`` is set to ``None``, it
    defaults to the :ref:`current time zone <default-current-time-zone>`. </s> remove     aware :class:`~datetime.datetime`
 </s> add     aware :class:`~datetime.datetime`. If ``timezone`` is set to ``None``, it
    defaults to the :ref:`current time zone <default-current-time-zone>`.

    .. versionchanged:: 1.8

        In older versions of Django, ``timezone`` was a required argument. </s> remove .. function:: make_aware(value, timezone)
 </s> add .. function:: make_aware(value, timezone=None) </s> remove def make_naive(value, timezone):
 </s> add def make_naive(value, timezone=None):
    .. versionchanged:: 1.8

        In older versions of Django, ``timezone`` was a required argument.

.. function:: make_naive(value, timezone=None)
  
      This function can raise an exception if ``value`` doesn't exist or is
      ambiguous because of DST transitions.
  
    .. versionchanged:: 1.8

        In older versions of Django, ``timezone`` was a required argument.

.. function:: make_naive(value, timezone=None)
  
      Returns an naive :class:`~datetime.datetime` that represents in
      ``timezone``  the same point in time as ``value``, ``value`` being an
      aware :class:`~datetime.datetime`
  
keep keep keep keep replace keep keep keep keep keep
 Fixed #23668 -- Changed make_aware() and make_naive() to use the current timezone by default

Thanks Aymeric Augustin for review. 
docs/ref/utils.txt