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
24497	Truncation of microseconds in DateTimeField leads to lookup trouble	Piotr Maliński	nobody	"I've stumbled upon an yet another inconsistency in Django forms with microseconds handling. 

I have a model with DateTime field set with timezone.now(). In a form this date is passed as hidden so that before save it can be verified that the content didn't changed during moderation. The problem is that timezone.now() sets microseconds, while datetime returned in form_valid is without microseconds and thus can't be used for direct lookup on that model field (and that what hurts)."	Bug	closed	Forms	1.7	Normal	fixed	microseconds	jiguromusha7@…	Ready for checkin	1	0	0	0	0	0