DateTimeFormat.parse() rejects four-digit years when pattern is 'M/d/yy'.

Bug #677650 reported by Marius Gedminas on 2010-11-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zope.i18n
Won't Fix
Undecided
Unassigned

Bug Description

I've a zope.schema.Date field in a z3c.form. It accepts dates like

    11/20/10

but rejects dates like

   11/20/2010

with an error of "The datetime string did not match the pattern u'M/d/yy'."

This is rather unfriendly; the date is clearly unambiguous and should be accepted.

Tres Seaver (tseaver) wrote :
Changed in zope.i18n:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers