Currently the behavior of assume_timezone is ambiguous: one might expect the given PrimitiveDateTime to be in UTC, another could expect the function to directly accept a PrimitiveDateTime which is in the destination timezone.
I think the way forward is to deprecate the function assume_timezone as soon as possible, forwarding users to the replacement assume_timezone_utc which assumes the PrimitiveDateTime is already in UTC. Also necessary is to provide a clear documentation on how this new replacement actually works and make it clear it takes UTC!
Currently the behavior of
assume_timezoneis ambiguous: one might expect the given PrimitiveDateTime to be in UTC, another could expect the function to directly accept a PrimitiveDateTime which is in the destination timezone.I think the way forward is to deprecate the function
assume_timezoneas soon as possible, forwarding users to the replacementassume_timezone_utcwhich assumes the PrimitiveDateTime is already in UTC. Also necessary is to provide a clear documentation on how this new replacement actually works and make it clear it takes UTC!