Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openpyxl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 233
    • Issues 233
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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

Mercurial Paris conference scheduled ! Main event : 2022-09-22. Call for papers deadline: 2022-06-17.

  • openpyxl
  • openpyxl
  • Merge requests
  • !54

Merged
Created Mar 19, 2015 by Bitbucket Importer@bitbucket_importerOwner

do not apply twice the decimal part during date conversion to gregorian calendar

  • Overview 3
  • Commits 1
  • Changes 2

Created originally on Bitbucket by ericgazoni (Eric Gazoni)

Was already merged in Bitbucket before import, marked as merged by the import user

there is a miscalculation happening when you're nearing midnight (e.g. 23:59:59.999999), but not quite there yet (e.g. the decimal part of the julian date rounds to the next day), jdcal will round to the next day, but openpyxl would apply the full decimal part, adding 23:59:59.99999.

This fix neutralizes openpyxl when jdcal has already done the "jump"

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: bitbucket/merged-pr-54