Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

datetime.timedelta Support #475

Merged
merged 4 commits into from
Jul 11, 2023
Merged

datetime.timedelta Support #475

merged 4 commits into from
Jul 11, 2023

Commits on Jul 8, 2023

  1. Support encoding/decoding timedelta objects 

    These are encoded to ISO8601 duration strings. Only `'D'`, `'H'`, `'M'`,
and `'S'` units are supported (no relative units like `Y` or `M`
(month)).
    @jcrist
    jcrist committed Jul 8, 2023
    Configuration menu
    Copy the full SHA
    9cb05a0 View commit details
    Browse the repository at this point in the history

  2. Add json.schema & inspect support for timedeltas

    @jcrist
    jcrist committed Jul 8, 2023
    Configuration menu
    Copy the full SHA
    24d4694 View commit details
    Browse the repository at this point in the history

  3. Document timedelta handling

    @jcrist
    jcrist committed Jul 8, 2023
    Configuration menu
    Copy the full SHA
    5708f66 View commit details
    Browse the repository at this point in the history

Commits on Jul 11, 2023

  1. Support decoding seconds as float/int to timedelta 

    If `strict=False` we also support decoding int/float values (or str
representations of these values) to `timedelta` types. Note that a
`double` cannot represent a timedelta with microsecond precision if
the value is > ~270 years. For true roundtrip support we recommend
serializing timedeltas as ISO 8601 strings.
    @jcrist
    jcrist committed Jul 11, 2023
    Configuration menu
    Copy the full SHA
    0f498c3 View commit details
    Browse the repository at this point in the history