indygreg / indygreg/python-zstandard
Intent to rewrite in Rust
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 642
- Forks
- 116
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Description
After learning Rust and seeing its obvious benefits for safety/security and ease of maintenance over C, I would prefer to not author any new C code wherever possible.
I believe implementing this Python extension in Rust instead of C has long-term benefits to the maintainability of the project.
Once #109 lands and Python 2.7 is no longer supported, my intent is to start rewriting C code in this project in Rust. (Getting Rust to work with Python 2.7 on Windows is a massive plain and effectively blocks writing Python extensions in Rust.)
I'm filing this issue toprovide a sounding board for people to raise concerns/support for this initiative.
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 by reviewing issue #110 and its discussion about rewriting the Python extension in Rust; no specific file, test, or entry point is named. A concrete scope and acceptance criteria would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python, rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100