Skip to content

Provide none-any version without C extension #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vit9696 opened this issue Mar 10, 2023 · 6 comments
Closed

Provide none-any version without C extension #74

vit9696 opened this issue Mar 10, 2023 · 6 comments

Comments

@vit9696
Copy link

vit9696 commented Mar 10, 2023

Statically-compiled python interpreter cannot load C extensions as they are dynamic libraries. Could you please provide a version without the C extension on pypi and/or at least an easy way to build it without patches?

@ionelmc
Copy link
Owner

ionelmc commented Mar 10, 2023

Try the SETUPPY_ALLOW_PURE env var.

@vit9696
Copy link
Author

vit9696 commented Mar 10, 2023

Thanks, will try. The second issue is that running setup.py requires setuptools_scm, which is optional when installing from a whl package.

@vit9696
Copy link
Author

vit9696 commented Mar 10, 2023

Tested. This partially works, on systems with non-statically linked python it still builds a dynamic library, which is undesired for unified testing.

@ionelmc
Copy link
Owner

ionelmc commented Mar 10, 2023

I can add a skip flag but I'd like to understand a bit ... in your statically-compiled python project how are you installing all the other dependencies? I'd expect you'd use other packages not just lazy-object-proxy....

@vit9696
Copy link
Author

vit9696 commented Mar 10, 2023

In a build script we download every package recursively from pypi and install via the following command:

/path/to/python3 -m pip install --no-build-isolation --no-index /path/to/setuptools_scm-7.1.0-py3-none-any.whl

TLS/full networking support is not included, so downloading from pypi within the python is not an option.

lazy-object-proxy is indeed one of the dependencies we had to install from some other package. I am not exactly sure which at the moment.

@ionelmc
Copy link
Owner

ionelmc commented Dec 15, 2023

Sorry, the env var is SETUPPY_FORCE_PURE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants