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
This function can potentially return the system's local time as if it was UTC (see warning in datetime docs, or in more detail in this blog). This will lead to at most an 11-hour offset, which is not a huge problem, but it would be easy to fix.
datetime.utcnow() is currently used to set the creation date (global attribute and in file names) in all timeseries_products code, and in ncwriter/imos_template.py
The text was updated successfully, but these errors were encountered:
This has been fixed for timeseries_products.
For ncwriter there was also an update required in the unittests, and an additional issue with Python 3.5 - so I've left this for later.
This function can potentially return the system's local time as if it was UTC (see warning in datetime docs, or in more detail in this blog). This will lead to at most an 11-hour offset, which is not a huge problem, but it would be easy to fix.
datetime.utcnow()
is currently used to set the creation date (global attribute and in file names) in all timeseries_products code, and in ncwriter/imos_template.pyThe text was updated successfully, but these errors were encountered: