global / nonlocal interference : is this a bug, a feature or a design hole ?
Open
Nobody has claimed this yet.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 32361 |
|---|---|
| Nosy | @bitdancer, @ilevkivskyi |
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-18.09:59:49.568>
labels = ['interpreter-core', 'type-bug']
title = 'global / nonlocal interference : is this a bug, a feature or a design hole ?'
updated_at = <Date 2017-12-20.16:10:15.703>
user = 'https://bugs.python.org/Camion'
bugs.python.org fields:
activity = <Date 2017-12-20.16:10:15.703>
actor = 'skrah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2017-12-18.09:59:49.568>
creator = 'Camion'
dependencies = []
files = []
hgrepos = []
issue_num = 32361
keywords = []
message_count = 21.0
messages = ['308537', '308570', '308580', '308610', '308611', '308623', '308641', '308642', '308644', '308679', '308680', '308682', '308683', '308695', '308701', '308703', '308722', '308730', '308731', '308743', '308745']
nosy_count = 3.0
nosy_names = ['r.david.murray', 'levkivskyi', 'Camion']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32361'
versions = ['Python 3.6']
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 the migrated BPO issue 32361 and its 21-message discussion, then review the Interpreter Core context and the reported Python 3.6 behavior. No source files or tests are identified, and completion is not defined; first establish whether the behavior is a bug, feature, or design issue before locating an appropriate change and regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100