Arch Linux User Repository

As python 3.8 was replaced by python 3.9, you could run into the following error:

Traceback (most recent call last):
  File "/usr/bin/stapler", line 5, in <module>
    from staplelib import main
ModuleNotFoundError: No module named 'staplelib'

To solve it, rebuild "python-pypdf2" and then "stapler". Then the directories for Python 3.9 should exist.

@oriba:

......QUOTE:it would make sense to have a list of features that really are needed as a minimal replacement for stapler (or pdftk)........

Could not agree more with you. A solid and reliable pdf tool that does this job is a must.

...... QUOTE: I started writing some pdf-tools for myself a while ago,....I might put them on github or so.....

Please do. I'd be happy to provide feedback help with docs etc... (no dev skills)

By the way, apropos PDF tooling, theres the Talk page, https://wiki.archlinux.org/index.php/Talk:PDF,_PS_and_DjVu on the excelent Arch Wiki PDF et al tools overview page

@m040601: oh, relly, they did it? Stapler undead?

In my eyes, the stapler-project is dead. Tried to contact the developer regarding some issues, and the release-numbering was one of the issues. Since months no answer. I started writing some pdf-tools for myself a while ago, nevertheless using stapler quite often. But maybe I will switch to my own tools completely one day. If other people would be interested, I might put them on github or so. But it would make sense to have a list of features that really are needed as a minimal replacement for stapler (or pdftk). At the moment I'm not sure what the current status of stapler is - which possibilities it offers, because I did not checked the current development version of it. Also the syntax of the commands maybe could be better. A Python3-release for Stapler is asked for by different peoples over months. So... a list of minimal commands might encourage me to write a new tool (or set of tools) for pdf-manipulation. Some kind of task-list for the Xmas holidays ;-)

I'm adopting the package now (unless someone else wants?). The release policy on upstream is a bit confusing, 0.3.2 is indeed newer than 0.4, but both are extremely outdated (2015). Python 3 compatibility came recently, but is only on head. I would wait a bit for the discussion here: https://github.com/hellerbarde/stapler/issues/51 Ideally, there will be an official release to which we can update. Otherwise, bypassing the release and switching to a Git commit would be a temporary workaround, although personally I would prefer an official release.

Please remove the python2 dependency. Not needed anymore:

https://github.com/hellerbarde/stapler/pull/55 This makes stapler Python 3 compatible while keeping compatibility with Python 2.7,

If looking on github, release 0.3.2 came after 0.4. Don't know why. But it seems to be more recent code, even though it also is old. Could you check, if the 0.3.2 is really newer and if so, could you please update the AUR-package?