You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although as of 1.7.0, deprecation of datetime.utcnow() was delt with by @RazerM ( 5273fa2 ), it seems like datetime.utcfromtimestamp() also requires some attention.
Warning: Because naive datetime objects are treated by many datetime methods as local times, it is preferred to use aware datetimes to represent times in UTC. As such, the recommended way to create an object representing a specific timestamp in UTC is by calling datetime.fromtimestamp(timestamp, tz=timezone.utc).
For context, stumbled upon the deprecation warning while unittesting dbt-core, as part of issue 9791. When drilling down the logs, ended up at:
Hello there,
Although as of 1.7.0, deprecation of
datetime.utcnow()
was delt with by @RazerM ( 5273fa2 ), it seems likedatetime.utcfromtimestamp()
also requires some attention.The official datetime docs point out:
For context, stumbled upon the deprecation warning while unittesting
dbt-core
, as part of issue 9791. When drilling down the logs, ended up at:logbook/src/logbook/compat.py
Line 143 in e7cc074
The text was updated successfully, but these errors were encountered: