mgedmin / mgedmin/check-python-versions
parse cibuildwheel configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Recentily I've found an useful package to build python on different OS/archs: [cibuildwheel](https://cibuildwheel.readthedocs.io/en/stable/).
It has [CIBW_BUILD, CIBW_SKIP](https://cibuildwheel.readthedocs.io/en/stable/options/#build-skip) configurations regarding python version used to build and test the package (locally and remotely).
Those configuration can be set as environment variables into github action or into pyproject.toml file.
E.g. as environment variable:
```
# Build python 3.10 3.11
CIBW_BUILD: cp310-* cp11-*
# Skip CPython 3.6 and CPython 3.7
CIBW_SKIP: cp36-* cp37-*
```
as pyproject.toml
```
# Build python 3.10 3.11
build= ["cp310-*", "cp11-*"]
# Skip CPython 3.6 and CPython 3.7
skip = ["cp36-*", "cp37-*"]
```
when using this package, it could be useful to add the extracted information to the final list.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the project currently extracts supported Python versions from configuration, then read cibuildwheel's CIBW_BUILD and CIBW_SKIP documentation and its environment-variable and pyproject.toml forms. Done means the extracted cibuildwheel configuration is included in the final list for both supported input styles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100