pypdf is back!

[MartinThoma]

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:

• PyPDF2 Ownership/Collaborators Available py-pdf/pypdf#657
• PyPDF2 cleanup py-pdf/pypdf#658
• [community poll] who is using PyPDF2?  py-pdf/pypdf#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.

[sfneal]

I'm in! I'm all for uniting these packages but my time for open source is limited at the moment.
https://github.com/sfneal/pdfconduit is another pdf package of mine which could be a candidate for moving to https://github.com/py-pdf.

[MartinThoma]

To all contributors of PyPDF3: Please feel free to add small PRs introducing changes that were added to PyPDF3 also to PyPDF2!

A good PR has the following properties:

1. It does one thing, and does it well: Try to keep the size of the PR small
2. It explains a little bit what it's about. Is it a bugfix? Is it a feature? Just a stylistic change? Why is it a good idea to add it?
3. It contains a unit test. If it's a bugfix, it contains a test that now succeeds but was failing before.

PyPDF3 is 63 commits ahead of PyPDF2. Maybe somebody could create a list of those commits:

• Commit hash
• commit title (first line)

Then we could keep track of what was added back with which PR.

[MartinThoma]

I've just updated the title: We move from PyPDF2 to pypdf.

The last release of PyPPDF2 (version 3.0.0) was just done.

The first release of the heavily improved pypdf==3.1.0 was also just done :-)