parse datetime in response?

[ninsbl]

Response of actinia requests may contain datetime values. Those are currently returned as string.
While it is easy to transform those to datetime objects, a question is whether e.g. the request_and_check function in utils.py should parse and datetime objects by default, using an object_hook for datetime here:

actinia-python-client/src/actinia/utils.py

Line 60 in 66e31a0

return json.loads(resp.text)

The object hook would look something like this:

from datetime import datetime


def datetime_hook(json_dict):
    for (key, value) in json_dict.items():
        try:
            json_dict[key] = datetime.fromisoformat(value)
        except:
            pass
    return json_dict

(...)

json.loads(response, object_hook=datetime_hook)

What do you think @mmacata

[ninsbl]

P.S.: The question popped up because I noticed that in STRDS management, datetime values are wrapped in double and single quotes:
like e.g: 'creation_time': "'2025-01-02 10:53:31.936226'"

But that is probably an actinia issue and not with the Python client....

[ninsbl]

OK, I see that the issue with single and double quotes occurs because t.info wraps all values that may contain spaces in single quotes, so shell output can be used with eval on the command line. So it is a GRASS GIS issue.... The question if datetime values should be parsed in the Python client is still worth considering...