pdfrw icon indicating copy to clipboard operation
pdfrw copied to clipboard
verified publisher icon pmaupin

Project status ?

Open allan-simon opened this issue 6 years ago • 8 comments

Has it has been exactly 2 years since the last commit, I would like to know if this project is still actively maintained before starting using it in a brand new project ? i.e so that if it does not work in python 3.9 or forward, or I find a bug and I submit a PR will it get merged and published in pypi ?

allan-simon avatar Feb 18 '20 22:02 allan-simon

I have been a bit busy to do this, but am still monitoring the issues. Could use some additional maintainers.

THanks, Pat

pmaupin avatar Feb 18 '20 23:02 pmaupin

awesome, thanks :)

allan-simon avatar Feb 19 '20 06:02 allan-simon

I'm sorry to say this but please don't use it in new projects. This is already broken on py3.7 (#199 shows some symptoms), and we've started removing the few packages that depend on it.

mgorny avatar Apr 20 '20 20:04 mgorny

Due to its current unmaintained state, pdfrw is now also flagged for removal from Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958362

josch avatar Apr 20 '20 21:04 josch

I'm sorry to see this project slowing down, it was great! But I appreciate the amount of work required to dance with a beast like the PDF spec.

For folks looking for a replacement, https://pikepdf.readthedocs.io has worked out well for me so far. It's not pure python, but the raw object API is very close to the one exposed by pdfrw (though it's Object / Array / Dictionary system took a little adjusting in some isinstance tests).

eli-collins avatar Sep 16 '20 19:09 eli-collins

Judging from this and similar threads and the commit history, I assume that the package has been abandoned? Given the network insights, https://github.com/sarnold/pdfrw appears to be the most active fork, although it has some untouched long-standing PRs has well.

stefan6419846 avatar Jan 24 '23 09:01 stefan6419846

Building upon my previous comment: Is there any general interest in keeping pdfrw maintained? Background: I thought about moving development to an organization here at GitHub to actually continue development (maybe starting with the fixes from the aforementioned fork). Nevertheless, this probably would at least require another additional maintainer.

stefan6419846 avatar Jan 25 '23 07:01 stefan6419846

I can talk for the situation in Debian as well as the author of img2pdf which (used to) use pdfrw.

  • since pdfrw is unmaintained right now, we removed it from Debian "testing" and thus it will not be part of the next Debian stable release this year: https://bugs.debian.org/958362
  • as a consequence, all software in Debian that used to use pdfrw (like rst2pdf) had its pdfrw support removed
  • in img2pdf I added pikepdf to replace pdfrw as the pdf engine

So all the stuff I'm working on stopped using pdfrw because it is unmaintained and moved to other solutions like pikepdf. If somebody resurrects pdfrw I would add it as a supported engine to img2pdf again but I'm not missing it.

josch avatar Jan 31 '23 09:01 josch