hey @Loufe can you check the release wheels to make sure I've added the correct ones, sorry there's so many, I went with the approach here https://github.com/pypa/cibuildwheel

@abetlen tested and working, LGTM! Good choice with Cibuildwheel.

I might suggest that until such a time as someone requests a wheel for another OS / Windows arch / Python version, we save Github some electricity and leave the release cleaner by limiting the build to specific wheels. According to Pypa there is a param to limit version "CIBW_BUILD", i.e.:
CIBW_BUILD: cp310-*

That said, I would even go so far as to limit the build to amd64:
CIBW_BUILD: cp310-win_amd64

By the way, I was wondering how to account for changing versions in Ooba's one-click installer batch. I wrote this call to adjust for current tag name - does this look ok to you? I guess more specifically, you don't plan on changing build formats at any points?

for /f "usebackq delims=" %%i in (`powershell -command "$url = 'https://api.github.com/repos/abetlen/llama-cpp-python/releases/latest'; $response = Invoke-RestMethod -Uri $url; $response.tag_name"`) do set TAG_NAME=%%i
call python -m pip install https://github.com/abetlen/llama-cpp-python/releases/download/%TAG_NAME%/llama_cpp_python-%TAG_NAME:~1%-cp310-cp310-win_amd64.whl

Tested CIBW_Build: cp310-* in a35a233, works as it should.

In any case you should close this PR (too many commits to undo gitignore change and wheels dir, etc.)
If you agree with limiting to 3.10, you should be able to integrate the .yaml modifications on your end from that commit easily.

@Loufe thanks! I'll leave the other wheels in case anyone needs them but I'll investigate which ones are completely redundent in the future.