Standard type codes for array.array, same as struct

Open
#53,312 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no implementation file, entry point, or test. Start by locating CPython's array.array and struct type-code handling and comparing their documented code sets; done should mean the intended standard codes are defined consistently with regression coverage.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 9066
Nosy @pfalcon, @mdickinson, @serhiy-storchaka, @MojoVampire

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 2010-06-24.04:58:28.910>
labels = ['type-feature', 'library']
title = 'Standard type codes for array.array, same as struct'
updated_at = <Date 2014-04-13.09:07:38.733>
user = 'https://bugs.python.org/cmcqueen1975'

bugs.python.org fields:

activity = <Date 2014-04-13.09:07:38.733>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-06-24.04:58:28.910>
creator = 'cmcqueen1975'
dependencies = []
files = []
hgrepos = []
issue_num = 9066
keywords = []
message_count = 4.0
messages = ['108501', '108510', '215758', '215760']
nosy_count = 5.0
nosy_names = ['pfalcon', 'mark.dickinson', 'cmcqueen1975', 'serhiy.storchaka', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue9066'
versions = ['Python 3.5']

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.