Michael Lorton mlorton@microsoft.com
Thu, 20 Feb 1997 11:28:42 -0800

Dates in Python really should have a "precision" , the way they do in
real life.  1996 is a date, right?  It just has a precision of one year.

There are some provocative questions:

1.  What does equality mean?  Does "noon today" "equal"  1997-02-20
12:00:00.0.  Does it equal "today"?  1997?

2.  If we allow (a form of) date-equality that means inclusion, D1 == D2
 IFF ( D1 contains D2 or D2 contains D1), what about timezones?  By this
definition 1997 in Seattle does not equal 1997 in Amsterdam, since there
is, what, nine hours overhand on each side.

3.  What about total-ordering?  Is 1997 in Amsterdam "less than" New
Years Day  in Seattle (because it started first), "equal to" (because it
overlaps) or "greater than" (because it ends last)?


DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org