Platform support and testing status about pypdfium2 HOT 14 CLOSED

macOS x86_64
・10.11.6

・10.15.7

are confirmed to work.

from pypdfium2.

Thanks for the fix.
V0.8.1 was successfully installed on macOS Big Sur(11.6) with Apple M1 chip.
And, all passed!

from pypdfium2.

Thanks, I've updated the status above

from pypdfium2.

OS: macOS Big Sur(11.6)
CPU: Apple M1

1. Python3.8.9(default pre-installed in Big Sur). Processing stopped in "Preparing metadata (setup.py)..."

2. Python3.10.1(Downloaded from python.org). Only pypdfium2-0.1.0 can be installed.
pip3 install -U pypdfium2

.

from pypdfium2.

Many thanks for testing again, this is really apprectiated.

As far as I can see, it was only an issue with wheel naming. I have pushed a commit that should fix it, and uploaded a new minor release that you can try: https://pypi.org/project/pypdfium2/0.8.1/ (pip3 install -U pypdfium2, as usual)
This should now download and install correctly with both Python versions.

from pypdfium2.

Super, thanks!

from pypdfium2.

Hi @mlove4u,
I recently made some changes to macOS wheel tags, which I believe will enable compatibility with more versions of macOS.
Just to make sure my changes did not break anything, could you please test again? You'll want to use the following command to install a beta version containing the changes:

python3 -m pip install -i https://test.pypi.org/simple/ pypdfium2==0.13.2

Testing macOS x86_64 would be sufficient to me (if this works, then the other one should probably do as well). However, if you also have access to ARM it would be really nice if you could try both.
You don't necessarily have to run the test suite - just confirming that the install does not fail is enough.
Thanks in advance.

from pypdfium2.

@mara004
There is no problem in macOS Big Sur(11.6.1) with Intel CPU. And I will test it in ARM later today.

from pypdfium2.

ARM(macOS Big Sur(11.6)) test also passed!

from pypdfium2.

Thanks for the quick response!

from pypdfium2.

I now added a workflow which tests those platforms that are currently provided by GitHub Actions.
This might increase confidence in our releases.

from pypdfium2.

@mlove4u Not sure if you are still interested in pypdfium2, but might I ask for your testing help with M1 once more?
I would like to find out whether pdf.save() works on M1, because it involves a writing callback, while M1 forbids write+execute memory.

Installing latest pypdfium2, running the test suite and sending me the output to check if this works or not would be really helpful.
I believe the saver test cases were only added shortly after #3 (comment) (Jan 12, but c76e892 was Jan 22).
Unfortunately, on the second case in February, you might not have run the test suite as I said it would be OK to only see if the wheel installed...

from pypdfium2.

@mara004 You are welcome. These are my environments , I run the test files and all passed!

1. Intel CPU, macOS Big Sur(11.7.10): passed
2. M1 macOS Ventura 13.2.1: passed
3. M2 macOS Sonoma14.1.1: passed

from pypdfium2.

Thanks for the quick response! Glad it passed.
jbarlow83 also mentioned that ctypes implements callbacks differently, so the problem seems to be limited to cffi.

from pypdfium2.