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
  • !34

Merged
Created Nov 17, 2014 by Bitbucket Importer@bitbucket_importerOwner

worksheet page setup modified

  • Overview 15
  • Commits 8
  • Changes 12

Created originally on Bitbucket by jphuart (jean pierre huart)

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

worksheet page setup modified to follow the same logic of the worksheet properties and to consider all available parameters.

What is proposed here is done keeping compatibility with the previous versions keeping the worksheet.page_setup as the combination of PageSetup and PrintOptions under it. But splitting the 2 will make code simplier, but will break legacy. Maybe it can be better managed than what I've done.

Small detail I'm not proud of it is the 'untuple' function in page.py module. It has been added to pass a series of tests using saved xlsx files that contains this parameters as tuples. I'm surprised they work correctly because I've the impression they don't follow the schema constraints.

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