id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
35097	Test utils.dateparse.parse_datetime() with a bare date	David Wobrock	nobody	"Hey,

A bit late to the party, but in 4.0, we introduced a patch that changed the behaviour of `django.utils.dateparse.parse_datetime`.
In very short, on Django 3.2
{{{
>>> from django.utils.dateparse import parse_datetime
>>> parse_datetime('2023-01-01')
# Returns None
}}}

And on Django 4.0,
{{{
>>> from django.utils.dateparse import parse_datetime
>>> parse_datetime('2023-01-01')
datetime.datetime(2023, 1, 1, 0, 0)
}}}

The change was introduced in [https://github.com/django/django/commit/f35ab74752adb37138112657c1bc8b91f50e799b f35ab74752adb37138112657c1bc8b91f50e799b], which relates to #32892.
The initial ticket considers mainly `parse_time` and `parse_date`, but not the impacts on `parse_datetime`.

I think this behaviour is valid, since a date without time can be considered a valid datetime object, with 0 as time values.
But since this change was not documented, I wanted to report it somewhere, because I couldn't find any other reference to it :)

Though I'm not sure this is the best way to share this information, so feel free to close the ticket."	Cleanup/optimization	closed	Utilities	4.0	Normal	fixed			Accepted	1	0	0	0	0	0