On Sat, Aug 22, 2015 at 6:28 PM, Tim Peters <[email protected]> wrote:
> [Chris Barker <[email protected]>] > > if it would be implemented by datetime, or a datetime subclass, wouldn't > it > > make sense for that attribute to be on the datetime instance, rather > than a > > tzinfo instance? > > Which is why arithmetic "belongs in" tzinfo too - how the local clock > acts is entirely about the timezone. > While this is a very logical conclusion, I find it challenging to explain why arithmetic selection flag "belongs" to tzinfo while the "local time disambiguation flag" "belongs" to the datetime instance. It feels backwards: DST is the stuff about timezones while arithmetic is the stuff about datetime. Yet, we have what we have. In an alternative universe, maybe we could have a DateTime metaclass that would produce a separate datetime class for each timezone and then tzinfo would be a class variable rather than instance member.
_______________________________________________ Datetime-SIG mailing list [email protected] https://mail.python.org/mailman/listinfo/datetime-sig The PSF Code of Conduct applies to this mailing list: https://www.python.org/psf/codeofconduct/
