-
Notifications
You must be signed in to change notification settings - Fork 1.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
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
[community poll] who is using PyPDF2? #659
Comments
|
I'm using it on Windows and Linux, with Python 2.7 and with Python 3.6 and 3.10. I noticed a bug in my fork just a few minutes ago. Feel free to include my changes here under the existing license if you like (but please wait until I've fixed that bug, which will happen next week). I'm using PyPDF for two purposes: |
Fixed. |
I've used pypdf4 with some fixes, evolutions. |
I've just added a test for extracting comments from PDFs. Thank you @pubpub-zz :-) |
@Joshua-IRT Uh, I was hoping that 3.6 and older isn't used any longer 🙈 Is pyenv an option for you? |
Does the code in master still work on |
Hi, AWS Lambda with Serverless framework |
I would drop official support for Python 3.5 and older. Most major projects did that a while ago (Django, Flask, Pandas, ...) My plan was to make one or two minor releases with many of the current PRs. Then deprecate 3.6 and older. If there are still many 3.6 users who cannot switch, maybe we can keep the support there. But I would like to avoid that. What do you think @MasterOdin ? |
Windows whatever the current is (10 I think) |
I also must say that I am glad this project is being revived and updated. |
Sorry, Python 3.6.8 is the main version on RHEL8. I have not tried pyenv on our systems yet, but can certainly look into it. Since Python 3.6 is end-of-life, though, I can certainly understand the desire not to support it (and agree with it). I guess implement what is easy to do in 3.6, make a final release that supports it, then deprecate. I can continue to use my hacked-together version until I get around to setting up pyenv, at least. |
openSUSE Leap 15.x
Nice to see progress again, we started using |
Windows 11
I am happy to contribute to the project if you want help - for example
Chris |
I use PyPDF3 but I'll say it is almost the same as PyPDF2 and if the community is moving back to PyPDF2 then it seems logical to migrate there too. operating system: what you use PyPDF2 for (reading/writing/manipulating PDFs? Maybe with a few details? What are core features to you? ): Projects now and possibly in the future read PDF contents, split and merge. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'll try to revive PyPDF2 in the next weeks. One part that is important to me is not to break existing / working features. Hence I'll introduce CI and will check the unit tests we have.
In order to test properly / think about a deprecation strategy, I need to have a grasp of who is using PyPDF2.
Please share:
The text was updated successfully, but these errors were encountered: