Roadmap for pypdf==4.0.0 #2041
Replies: 2 comments 3 replies
-
We could update the Sphinx theme as a signal that we're getting more modern. My requirements would be:
I know that "must look good" is very subjective. I'm open to suggestions and community upvotes 👍 / downovtes 👎 certainly influence me, but I will make the final decision. What I found:
|
Beta Was this translation helpful? Give feedback.
-
@pubpub-zz @stefan6419846 On first or second of January 2024 I'll add bigger PRs to do the deprecations. I will go through the open PRs beforehand and try to merge as many as possible. This is just a heads-up. Doing the deprecations will likely give several merge conflicts. I don't want to annoy you / cause unnecessary work for you. I'm looking forward to those cleanup-changes xD |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey :-)
I want to release
pypdf==4.0.0
in 2024 (but not earlier). This is a check-list for me. Please let me know if I should add anything.I want to do the following with
pypdf==4.0.0
(but not earlier):AES-256
(seeencryption-decryption.md
). That is a breaking change as it means thecryptography
package will be required.deprecate_with_replacement(removed_in="4.0.0")
: All of those function calls need to be replaced bydeprecation_with_replacement
.deprecate_no_replacement(removed_in="4.0.0")
: All of those function calls need to be replaced withdeprecation_no_replacement
deprecation_with_replacement(removed_in="3.0.0")
: All of those functions / modules can be completely removed. Remove the default value of the function itself.deprecation_no_replacement(removed_in="3.0.0")
: All of those functions / modules can be completely removed. Remove the default value of the function itself.Beta Was this translation helpful? Give feedback.
All reactions