Updating the Evaluation order section to cover *expression in calls
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 | 33492 |
|---|---|
| Nosy | @mjpieters, @lebigot |
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-05-14.08:14:24.843>
labels = ['3.7', '3.8', 'docs']
title = 'Updating the Evaluation order section to cover *expression in calls'
updated_at = <Date 2018-05-18.17:36:41.856>
user = 'https://github.com/mjpieters'
bugs.python.org fields:
activity = <Date 2018-05-18.17:36:41.856>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-05-14.08:14:24.843>
creator = 'mjpieters'
dependencies = []
files = []
hgrepos = []
issue_num = 33492
keywords = []
message_count = 1.0
messages = ['316494']
nosy_count = 3.0
nosy_names = ['mjpieters', 'docs@python', 'Eric Lebigot']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue33492'
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 with Python's documentation section on evaluation order and review issue 33492 for the intended coverage of * expressions in calls. Update that section to explain the relevant evaluation order, then verify the documentation is clear and accurate.
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
- 35/100