We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Both pypdf and pyHanko are dependencies. pyHanko includes a fork of PyPDF2, which is itself a fork of pypdf.
The pyHanko variants of the used pypdf objects (PdfReader, PdfWriter, PageObject) should be used.
Implementing this proposal enables to drop the pypdf dependency.
The text was updated successfully, but these errors were encountered:
PyPDF2, which is itself a fork of pypdf
This is wrong for some time now: PyPDF2 has been deprecated in favor of pypdf. pyHanko does indeed include a heavily modified version of PyPDF2.
In my personal opinion, 6777fe9 should be mostly reverted and pyHanko dropped completely for a clean separation of concerns.
Sorry, something went wrong.
It would also be useful if pyHanko was optional instead of removing the whole feature.
No branches or pull requests
Motivation
Both pypdf and pyHanko are dependencies. pyHanko includes a fork of PyPDF2, which is itself a fork of pypdf.
Proposed Solution
The pyHanko variants of the used pypdf objects (PdfReader, PdfWriter, PageObject) should be used.
Additional Context
Implementing this proposal enables to drop the pypdf dependency.
The text was updated successfully, but these errors were encountered: