DateTime parsing assumes "US" style mm/dd/yyyy

[Chui Tey]

The parsing heuristics assume that if a date time looks like this "11-01-2001", then it is November 11.
Actually at non-US sites, it is 11th of January.

--- a/Lib/site-packages/datetime-2.12.6-py2.7.egg/DateTime/DateTime.py
+++ b/Lib/site-packages/datetime-2.12.6-py2.7.egg/DateTime/DateTime.py

@@ -984,8 +986,12 @@ class DateTime:
                         month=ints[1]

             elif ints[0] <= 12:
- month=ints[0]
- day=ints[1]
+ if datefmt=="us":
+ day=ints[1]
+ month=ints[0]
+ else:
+ day=ints[0]
+ month=ints[1]
                 year=ints[2]
             del ints[:3]

[Lennart Regebro (regebro-gmail)]

This looks like it's already fixed in DateTime 3.0.

[Hanno Schlichting (hannosch)]

I fixed this on DateTime trunk (what will be 3.0.2). A different code path was taken there and it didn't respect the datefmt setting.

[Hanno Schlichting (hannosch)]

Released as part of DateTime 3.0.2, first included into the Zope 4 release line.