Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openpyxl
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 239
    • Issues 239
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • openpyxl
  • openpyxl
  • Merge requests
  • !398

Merged
Created Feb 27, 2021 by nmartensen@nmartensenContributor

Timedelta and iso_dates

  • Overview 0
  • Commits 2
  • Pipelines 1
  • Changes 2

When iso_dates is set to True, openpyxl does not really know what to do with timedeltas since the XLSX specification does not provide a suitable string representation for them. It currently divides the duration by full days, discards the integer ratio and converts the fractional day remainder to time of day. This makes it impossible to roundtrip timedelta values through files using iso_dates=True, in particular timedeltas of more than 24 hours.

Instead of doing the lossy conversion from timedelta to time, perhaps we can ignore the iso_dates property when storing timedelta.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: topic/3.0/iso_delta