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 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • 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
  • !340

Add support for writing custom color palettes

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Bitbucket Importer requested to merge topic/default/bitbucket-pr-340 into branch/2.6 May 22, 2019
  • Overview 5
  • Commits 13
  • Changes 16

Created originally on Bitbucket by Hannes Breul

Fixes a longstanding issue with xlsx files generated in Apple Numbers: When opening an existing file that has an internal color palette (`indexedColors`), the original color palette is dropped from the file and gets reset to the default, causing the colors to be off. With these changes, the color palette will be saved to the new file.

See also: https://stackoverflow.com/questions/48883829/when-i-save-a-openpyxl-it-changes-the-colour-of-all-the-rows-columns-text

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: topic/default/bitbucket-pr-340