On 01/08/2014 05:27 PM, Roy Smith wrote:
In article <[email protected]>,
Kevin Walzer <[email protected]> wrote:
I haven't updated my Python apps to 3.x because there's nothing in 3.x
that offers benefits to my users.
I almost found a reason to move to Python 3 today. Then I got smacked.
[snip]
Naive datetimes are what everybody uses. It's what utcnow() gives you.
So why make life difficult for everybody? Python 3 didn't win a convert
today.
Naive datetimes suffer from the same problem as the old str/unicode problems: as soon as you try to mix different
timezone datetimes that are naive, you have a mess (temporal-bake, anyone?).
--
~Ethan~
--
https://mail.python.org/mailman/listinfo/python-list
