On 08/31/2015 12:58 PM, Alexander Belopolsky wrote: > On Mon, Aug 31, 2015 at 2:38 PM, Carl Meyer <[email protected] > <mailto:[email protected]>> wrote: > [Tim Peters] > > > Nope. There's nothing here about, e.g., messing with datetime > > constructors, .replace(), .combine() ... "naive time" is left alone > > here. It's only timezone-specific operations targeted here, which are > > all implemented _by_ tzinfo objects. Not by datetime itself. > > There wasn't any of that stuff (messing with constructors, or replace, > or combine, or naive time) in what Alex and I were discussing in the > other thread, either. Just the idea of having `utcoffset()` raise an > error if it hit an ambiguity. > > > I think the main difference between Tim's current proposal and what was > previously discussed is that all older proposals somehow required a > third value for fold.
Yes, that's true. That's because (unless I'm misunderstanding) Tim is suggesting something far more audacious than I had considered: making "raise an error on ambiguity" the default behavior, instead of an opt-in choice. The extra value for `fold` was just the opt-in mechanism. Carl
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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/
