Local installation doesn't work after change in build system about yalafi

[torik42]

When I create a new conda environment (then python -c 'import yalafi' exists with an error), install YaLafi with python -m pip install . or pip install ., change the directory and try python -c 'import yalafi' again, it works. I will try to see where it fails in your action.

I can now reproduce locally, maybe I tricked myself and was still in the same directory. Will investigate further.

[torik42]

I just tested again with python 3.9 and pip 22.3 and pip install . as well as pip install --editable . work well. Which versions of python and pip are you using? I migrated to a more recent (introduced in PEP 518 in 2016) build configuration. Older versions of pip might be able to install the wheels from PyPI but cannot parse the information to build them. As a side effect, you cannot install with python setup.py install any more (which wasn’t recommended anyway to my knowledge).

[torik42]

Maybe my comment about the wheel is wrong. I haven’t yet published to PyPI. You could test with the version on test PyPI which can be installed with pip install -i https://test.pypi.org/simple/ yalafi==1.3.1b6. Does that work on your end?

[JulianGoeltz]

Are you sure it is working with just the pip install .? Because in the minimal example also with python 3.9 and pip 22.3 (before it was python 3.10 and pip 22.3) it fails to correctly install the package: to be precise, the install step goes through, but afterwards the package cannot be imported.
for the details, see https://github.com/JulianGoeltz/MWE_yalafi_20221101/actions/runs/3397400639/jobs/5649522110#step:4:12

I've added the testpypi install and that is not working either

all that happens in that action is that a new container is set up with a specific python version, pip is updated, and then yalafi is installed in different ways, with a subsequent test whether the package can be imported.
Because python installs sometimes are 'brittle', I thought it best to test it with the github actions, to make sure it's not some residual configuration in my system.
In another project, I have a workflow that checks this automatically, would you like me to create a PR to add such a workflow here as well?