On Sep 22, 2015 1:09 PM, "Alexander Belopolsky" < alexander.belopol...@gmail.com> wrote: > > > On Tue, Sep 22, 2015 at 3:32 PM, Guido van Rossum <gu...@python.org> wrote: >> >> it is broken, due to the confusion about classic vs. timeline arithmetic -- these have different needs but there's only one > operator. > > > I feel silly trying to defend a design against its author. :-) Yes, a language with more than one > symbol would not have some of these problems. Similarly a language with a special symbol for string catenation would not have a non-commutative + and non-distributive *. All I am saying is that I can live with the choices made in datetime.
Is there a good argument against at least deprecating inequality comparisons and subtraction between mixed timezone datetimes? It seems like a warning that would be likely to catch real bugs. -n
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
