Hongru/cibuildwheel
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/main' into poerty_problem

Browse Source
This commit is contained in:
Joe Rickerby
2023-06-23 08:46:51 +01:00
parent 1ce209198a 5ef9f081bd
commit 8f569c42ec
83 changed files with 1082 additions and 623 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/faq.md
+3 -3
View File
@@ -161,7 +161,7 @@ There are two suggested methods for keeping cibuildwheel up to date that instead
If you use GitHub Actions for builds, you can use cibuildwheel as an action:
```yaml
uses: pypa/cibuildwheel@v2.12.0
uses: pypa/cibuildwheel@v2.13.1
```
This is a composite step that just runs cibuildwheel using pipx. You can set command-line options as `with:` parameters, and use `env:` as normal.
@@ -183,7 +183,7 @@ The second option, and the only one that supports other CI systems, is using a `
```bash
# requirements-cibw.txt
cibuildwheel==2.12.0
cibuildwheel==2.13.1
```
Then your install step would have `python -m pip install -r requirements-cibw.txt` in it. Your `.github/dependabot.yml` file could look like this:
@@ -327,7 +327,7 @@ Solutions to this vary, but the simplest is to use pipx:
# most runners have pipx preinstalled, but in case you don't
python3 -m pip install pipx
pipx run cibuildwheel==2.12.0 --output-dir wheelhouse
pipx run cibuildwheel==2.13.1 --output-dir wheelhouse
pipx run twine upload wheelhouse/*.whl
```