realpython / realpython/python-guide
Non-CPython support for C-extensions
Nobody has claimed this yet.
- Dominant language
- Batchfile
- Stars
- 29.8k
- Forks
- 5.9k
- PR merge metrics
- No merged PRs in 30d
Description
From https://github.com/realpython/python-guide/blob/master/docs/starting/which-python.rst#cpython :
If you are writing open-source Python code and want to reach the widest possible audience, targeting CPython is best. To use packages which rely on C extensions to function, CPython is your only implementation option.
PyPy now supports (some/all?) C extensions
http://doc.pypy.org/en/latest/extending.html
Jython supports C extensions through JyNI:
https://github.com/Stewori/JyNI
IronPython supports C extensions now?
https://ironpython-test.readthedocs.io/en/latest/extending/extending.html
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 in docs/starting/which-python.rst at the CPython section and review the linked PyPy, JyNI, and IronPython extension documentation. Confirm the current scope of C-extension support for each implementation, then update the statement so it accurately describes the available options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100