Skip to content

Labels

Labels

  • A planned breaking change
  • Reported issues that might exist, but are impossible to solve as we cannot reproduce them
  • Pull requests that update a dependency file
  • This issue is a good starting point for first-time contributors
  • The generic submodule is affected
  • Pull requests that update GitHub Actions code
  • A minimal, complete and verifiable example helps a lot to debug / understand feature requests
  • We appreciate help everywhere - this one might be an easy start!
  • From a users perspective, this is a bug - a violation of the expected behavior with a compliant PDF
  • Issue related to CJK (Chinese-Japanese-Korean)
  • A feature request
  • Anything that is just internal: Simplifying code, syntax changes, updating docs, speed improvements
  • Anything related to PDF/A compliance
  • Rather a question than an issue. Should usually be a Discussion instead
  • Regression introduced as a side-effect of another change
  • From a users perspective, this is about robustness
  • Use this label only for issues caused by broken PDF documents that cannot be recovered.
  • Could be a bug, but also a robustness issue
  • The MCVE was added to PyPDF2 test suite
  • The PR/issue cannot be handled as issue and needs to be improved
  • The PR/issue needs more discussion before we can continue
  • The issue needs a minimal and complete (e.g. all imports) example showing the problem
  • The issue needs a PDF file to show the problem
  • This PR cannot be merged as the main branch is too different. You need to rebase or merge main.
  • A test should be added before this PR is merged.
  • Non-functional change: Continuous Integration
  • Non-functional change: Documentation