[Akira Li <[email protected]>] > ... > To be clear, it is not a suggestion to change anything in stdlib. It was > a reaction to the earlier message in this thread, to point out why > stdlib's fromutc() API is not the example that should be followed. Thank > you for providing the explicit reasons for the specific choices in the > API design: "redundency helps" and fromutc() is semi-private. I can't > remember when I've used fromutc() directly (It is used indirectly via > datetime.now(tz), datetime.fromtimestamp(ts, tz), d.astimezone(tz),
Which are part of Python. > tz.normalize()). Which is unique to pytz. So, yes, it's used as intended, by _implementations_ of higher-level methods. In those contexts, "convenience" is of no importance, but the value of catching errors (by implementers!) is of supreme importance. _______________________________________________ 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/
