v3.6.6
#184
Replies: 1 comment
-
WARNING: DO NOT INSTALL VERSION 3.6.6! Nothing in my automated testing showed any problems with the release, yet a critical ruamel.yaml patch file failed to be included in the package. This has caused version 3.6.6 to be entirely unusable. Please skip to version 3.6.7, which appears to include the missing file. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Enhancements:
Bug Fixes:
per http://yaml.org/type/timestamp.html.
Thanks again go to https://github.com/AndydeCleyre!
YAML/JSON/Compatible data. So, when the timestamp value contains time-zone
data, it will be stripped off after it is applied to the timestamp value.
The yamlpath library reverses this when emitting the affected values but if
you attempt to load the timestamp values directly in the DOM, you'll end up
with the UTC-converted value, stripped of any time-zone specification. If
you need the original, unmodified data as a time-zone aware
datetime.datetime value, pass it through the helper method,
Nodes.get_timestamp_with_tzinfo(data: AnchoredTimeStamp).
on the python-dateutil library. Be sure to install it!
This discussion was created from the release v3.6.6.
Beta Was this translation helpful? Give feedback.
All reactions