PyPDF4
PyPDF4 copied to clipboard
claird
PyPDF4 is dead
PyPDF4 is dead:
- Last release on PyPI: 2018
- Last commit in this repo: 2020
- Last response to an issue: ... I couldn't find any
I suggest to do one of the following:
- a) Delete it from PyPI + delete this repository
- b) Add a note at the top of the README that the project is no longer active + add the trove classifier
Development Status :: 7 - Inactive+ make a "final" release on PyPI + Archive the github repository
Agreed. I would prefer to see development focussed on PyPDF2 and there is an issue discussing its future here: https://github.com/mstamy2/PyPDF2/issues/657
I've produced a fork with new features/corrections. I did not had time yet to publish it further. What's your opinion about it ? https://github.com/pubpub-zz/PyPDF4
It's awesome when people like you put their time into such projects!
We have a couple of pdf libraries already and I have to think about xkcd:
I would like it a lot more if we had less pdf projects with a bigger community behind them
It's awesome when people like you put their time into such projects!
We have a couple of pdf libraries already and I have to think about xkcd:
I would like it a lot more if we had less pdf projects with a bigger community behind them
pyPdf4 was the most advanced/active mid 20, this is why I worked on. My 'Fork' is a set of fixes/improvement,I've proposed as contribution to @claird,like as some other did. You're proposal to delete this fork which. If you are willing to help all of us to keep alive pypdf4, I will be personnally very happy 😄
PyPDF2 is back!
I've just got the permissions on https://github.com/mstamy2/PyPDF2 and on pypi for PyPDF2.
I would love if we could unite the various pdf packages and build something great together
Some issues you might be interested in:
- https://github.com/mstamy2/PyPDF2/issues/657
- https://github.com/mstamy2/PyPDF2/issues/658
- https://github.com/mstamy2/PyPDF2/issues/659
I'm also thinking about moving the projects in the github organization https://github.com/py-pdf. That could especially be interesting if we want to merge PyPDF2 / pypdf3 into one project in the long run.
My 2 cents, I would really hate to see this repo/forked deleted. If someone is relying on it deleting it and forcing people to update working code to now work with PyPDF2 is a needless overhead. I'm grateful to all the forks for the contributions made (in spite of the difficulty in finding the one true PDF lib ;)) and I'm really happy to hear @MartinThoma is organizing a sustainable maintained version of PyPDF.
My preference would be to archive this repo, ideally with a readme update. It's clearly marked as a fork of PyPDF2 so even if it is not archived/updated it is easy for people to discover the upstream maintained version :-)
