The provided wheels faultily report to be pure Python

[mrossinek]

I would like to raise the issue symengine/symengine.py#474 to this repo because I believe that the fix for this requires some changes to how the Python wheels are built.

There is a lot in that discussion so let me try to summarize the key points:

• Since v0.10.0 of symengine some problems occur with symengine wheels on specific platforms and environment setups (see PDM and Poetry can't install symengine properly symengine.py#474 (comment))
• The problem is related to whether or not lib and lib64 are symlinked and whether the wheel reports to be pure Python or not (see PDM and Poetry can't install symengine properly symengine.py#474 (comment) and following comments).

The symengine wheels report as pure Python, although they are not, which I believe has to be fixed for this issue to be resolved. Unfortunately, I do not have the expertise to fix this in the build system of symengine but maybe the maintainers of this repository could help with that.

I see that there have been efforts in the past to part the build setup to scikit-build, which might prove to be a good path forward:

• [WIP] [PROPOSAL] use scikit-build for packaging symengine.py#144
• Switch to scikit-build symengine.py#219

Cc @martinruefenacht

[jlapeyre]

bump?

[garrison]

This bug is commonly encountered when using symengine on Fedora-based systems (including RHEL), under virtualenv or tox (which uses virtualenv under the hood, I have heard). The below Dockerfile shows how simple it is to reproduce, and it makes symengine impossible to uses under these circumstances.

FROM fedora:40
RUN dnf install -y pip
RUN pip install virtualenv
RUN virtualenv myenv
RUN ./myenv/bin/pip install symengine
RUN ./myenv/bin/python -c 'import symengine'

This test case can be reproduced by installing docker, placing the above text in a Dockerfile in its own directory, and running docker build . from that directory.

STEP 6/6: RUN ./myenv/bin/python -c 'import symengine'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "//myenv/lib/python3.12/site-packages/symengine/__init__.py", line 12, in <module>
    import symengine.lib.symengine_wrapper as wrapper
ModuleNotFoundError: No module named 'symengine.lib.symengine_wrapper'
Error: building at STEP "RUN ./myenv/bin/python -c 'import symengine'": while running runtime: exit status 1

[isuruf]

Switching to scikit-build would be the best way forward

[mrossinek]

I assume that this issue has also been resolved by symengine/symengine.py#511, thank you, isuruf!

I have not yet had the time to test this fix. Any chance there will be a new PyPI version released with it soon?

[isuruf]

wheels should be up now