Improve scope example in Tutorial, chapter 9
Open
Nobody has claimed this yet.
3.8 (EOL)
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38675 |
|---|---|
| Nosy | @terryjreedy |
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 2019-11-03.20:32:41.315>
labels = ['type-feature', '3.8', 'docs']
title = 'Improve scope example in Tutorial, chapter 9'
updated_at = <Date 2019-11-08.22:58:43.013>
user = 'https://bugs.python.org/DavidGoldsmith'
bugs.python.org fields:
activity = <Date 2019-11-08.22:58:43.013>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-11-03.20:32:41.315>
creator = 'David Goldsmith'
dependencies = []
files = []
hgrepos = []
issue_num = 38675
keywords = []
message_count = 2.0
messages = ['355908', '356272']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'docs@python', 'David Goldsmith']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue38675'
versions = ['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 reading the Python Tutorial, chapter 9, and the linked BPO issue 38675 to understand which scope example needs improvement. Done means updating that example so the intended scope behavior is clearer, then verifying the surrounding tutorial text remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100