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
While the existing datetime support is nice, some additional flexibility would be nice. When reading date strings, for example, the ability to use a well known parser such as dateutil.parser or, the ability to manipulate the datetime object as it's created (such as making sure the conversion to UTC happens correctly, if needed), or even to instantiate a datetime from a non-human format, such as a unix timestamp.
To that end, in addition to the dateformat metadata that exists today, maybe some sort of datefactory or dateformatter metadata, which would be a callable, passing in the value, and returning a well-formed datetime object would be useful.
The text was updated successfully, but these errors were encountered:
While the existing datetime support is nice, some additional flexibility would be nice. When reading date strings, for example, the ability to use a well known parser such as dateutil.parser or, the ability to manipulate the datetime object as it's created (such as making sure the conversion to UTC happens correctly, if needed), or even to instantiate a datetime from a non-human format, such as a unix timestamp.
To that end, in addition to the
dateformat
metadata that exists today, maybe some sort ofdatefactory
ordateformatter
metadata, which would be a callable, passing in the value, and returning a well-formed datetime object would be useful.The text was updated successfully, but these errors were encountered: