Marc-Andre Lemburg <m...@egenix.com> added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment: > > On Fri, Jul 2, 2010 at 6:00 PM, Tim Peters <rep...@bugs.python.org> wrote: >> >> Tim Peters <tim.pet...@gmail.com> added the comment: >> >>> Do you remember why it was a good idea to >>> derive datetime from date? >> >> Why not? A datetime is a date, but with additional behavior. Makes >> inheritance conceptually natural. > > It is also time with additional behavior. In the face of ambiguity ... > > Why not? See issue #5516. Most of datetime comparison code is > devoted to fighting inheritance from date. There is hardly any > non-trivial method that benefits from this inheritance. > > To me, conceptually, datetime is a container of date, time and > optionally time zone, it is not a date.
Just an aside: Conceptually, you don't need date and time, only an object to reference a point in time and another one to describe the difference between two points in time. In mxDateTime I called them DateTime and DateTimeDelta. What we commonly refer to as date is really the combination of a DateTime value pointing to the start of the day together with a DateTimeDelta value representing one full turn of the Earth. That said, I don't think redesigning the datetime module is part of this ticket, just adding a second implementation of what we already have in CPython :-) ---------- title: Add pure Python implementation of datetime module to CPython -> Add pure Python implementation of datetime module to CPython _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7989> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
