struct.pack(): trailing padding bytes on x64

Open
#70,933 6 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the issue title and the linked BPO issue 26746 to reconstruct the reported struct.pack() behavior on x64. Inspect the relevant CPython extension-module implementation and determine what behavior must change for trailing padding bytes; the issue is done when the x64 result matches the intended struct layout.

Written by the indexing model from the issue text.

Description

3.7 (EOL) extension-modules type-bug
BPO 26746
Nosy @mdickinson, @skrah, @meadori, @vadmium, @eric-wieser

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 2016-04-13.08:38:49.170>
labels = ['extension-modules', 'type-bug', '3.7']
title = 'struct.pack(): trailing padding bytes on x64'
updated_at = <Date 2019-04-21.07:32:27.586>
user = 'https://github.com/skrah'

bugs.python.org fields:

activity = <Date 2019-04-21.07:32:27.586>
actor = 'skrah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2016-04-13.08:38:49.170>
creator = 'skrah'
dependencies = []
files = []
hgrepos = []
issue_num = 26746
keywords = []
message_count = 6.0
messages = ['263315', '263322', '263328', '265213', '269887', '309085']
nosy_count = 6.0
nosy_names = ['mark.dickinson', 'skrah', 'meador.inge', 'martin.panter', 'Eric.Wieser', 'Allan Haldane']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26746'
versions = ['Python 3.7']

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.