Add docs about Embedding with an frozen module limitation.
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32353 |
|---|---|
| Nosy | @AraHaan |
| PRs |
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 2017-12-17.20:09:34.639>
labels = ['3.7', '3.8', 'docs']
title = 'Add docs about Embedding with an frozen module limitation.'
updated_at = <Date 2017-12-17.20:09:59.825>
user = 'https://github.com/AraHaan'
bugs.python.org fields:
activity = <Date 2017-12-17.20:09:59.825>
actor = 'Decorater'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2017-12-17.20:09:34.639>
creator = 'Decorater'
dependencies = []
files = []
hgrepos = []
issue_num = 32353
keywords = ['patch']
message_count = 1.0
messages = ['308497']
nosy_count = 2.0
nosy_names = ['docs@python', 'Decorater']
pr_nums = ['4910']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue32353'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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 pull request #4910 and the Python documentation areas covering embedding and frozen modules; the issue names no specific file or test. Done means the frozen-module limitation is documented clearly in the appropriate embedding documentation, with the existing pull request's status and proposed wording checked first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100