build and publish a wheel
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, release
Research direction
Inspect the repository's packaging configuration and existing automation to find where releases are built and published. Run uv build to confirm it produces both distributions, then verify that the publishing workflow uploads the wheel alongside the source distribution.
Written by the indexing model from the issue text.
Description
Currently only a source distribution is published. Best practice is to publish both sdist and wheel.
I did not find a workflow in this repository or I would have submitted a pull request.
I see that you use uv. Just uv build is all you want, building both distributions is the default behaviour.
- Dominant language
- Python
- Stars
- 26
- Forks
- 81
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 12
Contributor guide
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.
More from RedHatQE/openshift-python-wrapper
-
Dependency Dashboard OpenStale
Difficulty 4/5 3-5 days Newbie friendliness 15/100
RedHatQE/openshift-python-wrapper#2180 · 125 comments ·
All issues in RedHatQE/openshift-python-wrapper
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100