Tony Rice <rtpho...@gmail.com> added the comment:
This enhancement request should be reconsidered. Yes it is the documented behavior but that doesn't mean it's the right behavior. Functions should work as expected not just in the context of the module they are implemented in but the context of the problem they are solving. The suggested workaround of essentially nesting the specified UTC time via datetime.now(timezone.utc) is ugly rather than beautiful, complex rather than simple, and nested instead of flat. The suggestion that now is preferred over isnow loses sight that UTC is not like other timezones. A lot has changed since Python 2.7 was released in 2010. It is the default timezone of cloud infrastructure. ---------- nosy: +rtphokie _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue12756> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
