(Sonar) Fixed finding: "Using timezone-aware "datetime" objects should be preferred over using "datetime.datetime.utcnow" and "datetime.datetime.utcfromtimestamp""

[pixeebot]

Remediation

This change fixes "Using timezone-aware "datetime" objects should be preferred over using "datetime.datetime.utcnow" and "datetime.datetime.utcfromtimestamp"" (id = python:S6903) identified by Sonar.

Details

Some datetime object calls use the machine's local timezone instead of a reasonable default like UTC. This may be okay in some cases, but it can lead to bugs. Misinterpretation of dates have been the culprit for serious issues in banking, satellite communications, and other industries.

The datetime documentation explicitly encourages using timezone aware objects to prevent bugs.

Our changes look like the following:

 from datetime import datetime
 import time

- datetime.utcnow()
- datetime.utcfromtimestamp(time.time())
+ datetime.now(tz=timezone.utc)
+ datetime.fromtimestamp(time.time(), tz=timezone.utc)

More reading

• https://docs.python.org/3/library/datetime.html
• Using timezone-aware "datetime" objects should be preferred over using "datetime.datetime.utcnow" and "datetime.datetime.utcfromtimestamp"

🧚🤖 Powered by Pixeebot

Feedback | Community | Docs | Codemod ID: sonar:python/timezone-aware-datetime

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud