elena56brown
05 Mar 2025, 08:22
( Updated at: 10 Mar 2025, 08:38 )
Hello, It looks like the deprecation of datetime.utcnow() in Python 3.12 has caused some issues with your code2. The new recommended way to get the current UTC time is to use datetime.now(timezone.utc).
As for the ProtoOAGetTrendbarsReq returning None data, it seems like others have encountered similar issues. This might be related to the deprecation of UTCNOW and how the API handles the new datetime format.
Here are a few steps you can take to troubleshoot and resolve the issue:
Update your code: Ensure that you are using datetime.now(timezone.utc) instead of datetime.utcnow().
Check API documentation: Verify if there are any updates or changes in the API documentation regarding the datetime format.
Test with different datetime formats: Experiment with different datetime formats to see if the API accepts any specific format.
elena56brown
05 Mar 2025, 08:22 ( Updated at: 10 Mar 2025, 08:38 )
Hello,
It looks like the deprecation of datetime.utcnow() in Python 3.12 has caused some issues with your code2. The new recommended way to get the current UTC time is to use datetime.now(timezone.utc).
As for the ProtoOAGetTrendbarsReq returning None data, it seems like others have encountered similar issues. This might be related to the deprecation of UTCNOW and how the API handles the new datetime format.
Here are a few steps you can take to troubleshoot and resolve the issue:
Update your code: Ensure that you are using datetime.now(timezone.utc) instead of datetime.utcnow().
Check API documentation: Verify if there are any updates or changes in the API documentation regarding the datetime format.
Test with different datetime formats: Experiment with different datetime formats to see if the API accepts any specific format.
Hope this helps!
Best regards,
Elena
@elena56brown