Publish sdist with releases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, release
Research direction
Start by inspecting the repository's packaging and release configuration to find where binary wheels are built and published. Confirm how an sdist can be added to that process, then verify that a release publishes the source tarball alongside the existing wheels and that it can be used to build the package on unsupported platforms.
Written by the indexing model from the issue text.
Description
Would a change to also make a sdist tarball get published for releases be accepted?
Currently the abi3 binary wheels are great (much better than a bunch of CPython interpreter version specific wheels), though it doesn't give a way for people to install the wheel that are using PyPy. Alternate pip indexes for specific platforms not supported by PyPI such as piwheels.org and Pyodide also need an sdist in order to build wheels from PyPI.
Having an sdist also means I can install die-python on systems with CPUs that currently don't have binary wheels published, such as ppcle64 and risc-v systems. For releasing other software that depends on die-python this is particularly helpful, since PyPI doesn't allow uploading packages that have dependencies installed via direct git/http URLs.
- Dominant language
- Python
- Stars
- 88
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·