Docs: Clarify behavior for no abi3-pyXY
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
Please update the abi3 documentation to explain what happens if only the abi3 feature, but no abi3-pyXY feature is set. Does abi3-only have sensible behavior or should it be avoided?
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.
Research direction
Start with the linked abi3 documentation section in building-and-distribution.html and inspect how the abi3 and abi3-pyXY features are described. Verify the behavior when only abi3 is enabled, then update the documentation to state whether that configuration is sensible or should be avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100