➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, jackdied, jess.austin, mark.dickinson, ncoghlan
Date 2010-04-21.18:46:24
SpamBayes Score 7.2724156e-08
Marked as misclassified No
Message-id <n2id38f5331004211146l6444f3f7k486f40b1e2090acf@mail.gmail.com>
In-reply-to <1271874830.95.0.64288973065.issue5516@psf.upfronthosting.co.za>
Content 
On Wed, Apr 21, 2010 at 2:33 PM, Jess Austin <report@bugs.python.org> wrote:
..
> It might seem like the latter behavior is marginally better, but really this is just a mess, since a date-datetime comparison TypeErrors in all
> directions.  I appreciate Alexander's more experienced perspective, but it's not obvious to me that this problem is insoluble simply due to OOP
> algebra.  I'm going to keep tinkering with this to see if there isn't a way to satisfy his concerns AND fix these bugs WITHOUT breaking the
> established (and admittedly anti-OOP) behavior that dates are not equal to datetimes.
>

I certainly don't have a proof that this is impossible, so best of
luck.  Note, however that the problematic behavior is due to D/DT
classes implementor's choice not to derive DT from D.  Whether
resulting violation of the symmetry of equality is a bug in python or
D/DT implementation is at least an open question.
History
Date User Action Args
2010-04-21 18:46:26Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, mark.dickinson, ncoghlan, jackdied, jess.austin
2010-04-21 18:46:24Alexander.Belopolskylinkissue5516 messages
2010-04-21 18:46:24Alexander.Belopolskycreate