Replies: 1 comment 4 replies
-
@hjmallon Definitely seems useful as an optional include similar to how we handle the STL Filesystem library. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current
std::chrono::system_clock
conversion loses information during it's conversion to and from Pythondatetime
objects. In C++ we have a count of time since epoch, and an assumption that when writing that time out we will use the system local timezone. When converted to the python type we do not attach the timezone information used when creating it, so we cannot convert to UTC without extra information (i.e. what was the system timezone when the timestamp was converted from C++ to Python).Would it make sense to add this?
I also looked at using the C++ 20 std::chrono::utc_clock but it is not supported in some of the compilers I use yet.
Beta Was this translation helpful? Give feedback.
All reactions