Installation failures within a Docker container, problem with ctypesgen? about pypdfium2 HOT 3 CLOSED

Thank you for your reply. I used 'pip3 install git+https://github.com/pypdfium2-team/pypdfium2'.

from pypdfium2.

AFAICS, this will be a reoccurrence of #264 (comment):

Setup requires our fork of ctypesgen, which has recently received API-breaking changes. The latest release is still authored for the old codebase, however the main branch is updated. As a workaround, I'd suggest to just install from main using pip3 install git+https://github.com/pypdfium2-team/pypdfium2.

I'm currently making efforts to overhaul the ctypesgen codebase, which inevitably involves API-breaking changes.
Unfortunately this means the current latest release is not installable from source ATM.

Again, as in the linked issue, I don't understand why the wheel wasn't used and a source install happened, though...

Update: Previously this post complained about the edited issue template and missing debug info. However, taking a step back I acknowledge it was not overly applicable here. Two of the commands would fail, and the platform we can deduce from the Dockerfile. Apologies.

from pypdfium2.

I've implemented something to pin ctypesgen to an exact commit when building the sdist, which should prevent future occurrences of this type of issue.

pyproject.toml doesn't support env var substitution, which makes the matter slightly inconvenient.
Also we have to use the github API, because git itself to my knowledge doesn't support getting a branch head sha of a remote repo.

from pypdfium2.