how to migrate a c-extension module to one that supports subinerpreters?
Open
Nobody has claimed this yet.
docs
topic-C-API
topic-subinterpreters
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35420 |
|---|---|
| Nosy | @jkloth, @encukou, @ericsnowcurrently, @mattip |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2018-12-05.19:16:39.226>
labels = ['type-feature', 'docs']
title = 'how to migrate a c-extension module to one that supports subinerpreters?'
updated_at = <Date 2018-12-19.16:23:37.623>
user = 'https://github.com/mattip'
bugs.python.org fields:
activity = <Date 2018-12-19.16:23:37.623>
actor = 'petr.viktorin'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-12-05.19:16:39.226>
creator = 'mattip'
dependencies = []
files = []
hgrepos = []
issue_num = 35420
keywords = []
message_count = 2.0
messages = ['331142', '332149']
nosy_count = 5.0
nosy_names = ['jkloth', 'petr.viktorin', 'docs@python', 'eric.snow', 'mattip']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue35420'
versions = []
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 reading the linked BPO issue 35420 and the existing CPython documentation on C extensions and subinterpreters. Identify where migration guidance belongs and define done as a clear explanation of how a C-extension module can be adapted to support subinterpreters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100