You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
llvmlite is a simple binding layer for LLVM library. Wheels are statically linked an include binary LLVM library. Main consumer is a Python JIT library called Numba: https://pypi.org/project/numba/
How large is each release?
last release was around 673MB - mainly wheels, source is negligible, four python versions and 5 architectures -- two linux, two osx and one win.
Main size comes from statically including LLVM library. We have taken care to include only those bits needed for running a JIT compiler. Including this makes it possible for users to pip install numba and ave this just work w/o having to use a platform specific package manager to install or compile the LLVM library.
How frequently do you make a release?
About 2-4 times a year with one to two release candidates
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project URL
https://pypi.org/project/llvmlite/
Does this project already exist?
New limit
10GB
Update issue title
Which indexes
PyPI
About the project
llvmlite is a simple binding layer for LLVM library. Wheels are statically linked an include binary LLVM library. Main consumer is a Python JIT library called Numba: https://pypi.org/project/numba/
How large is each release?
last release was around 673MB - mainly wheels, source is negligible, four python versions and 5 architectures -- two linux, two osx and one win.
Main size comes from statically including LLVM library. We have taken care to include only those bits needed for running a JIT compiler. Including this makes it possible for users to
pip install numba
and ave this just work w/o having to use a platform specific package manager to install or compile the LLVM library.How frequently do you make a release?
About 2-4 times a year with one to two release candidates
Code of Conduct
The text was updated successfully, but these errors were encountered: