Limit "global" keyword name conflicts in language spec to those enforced by CPython

Open
#58,749 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the migrated BPO issue 14544 and the linked PRs gh-126523 and gh-126738. No source files or tests are named, so use those records to determine the language-spec wording in scope and the acceptance criteria for completion.

Written by the indexing model from the issue text.

Description

3.11 3.12 3.13 docs easy type-feature
BPO 14544
Nosy @rhettinger, @terryjreedy, @ncoghlan, @ezio-melotti, @merwok, @alex

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 2012-04-11.04:46:30.833>
labels = ['type-feature']
title = 'Limit "global" keyword name conflicts in language spec to those enforced by CPython'
updated_at = <Date 2015-03-05.10:03:11.434>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2015-03-05.10:03:11.434>
actor = 'ezio.melotti'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2012-04-11.04:46:30.833>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 14544
keywords = []
message_count = 4.0
messages = ['158005', '158006', '158007', '237252']
nosy_count = 8.0
nosy_names = ['rhettinger', 'terry.reedy', 'ncoghlan', 'fossilet', 'ezio.melotti', 'eric.araujo', 'alex', 'cvrebert']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14544'
versions = ['Python 3.5']

Linked PRs
  • gh-126523
  • gh-126738
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.