Optimize marshal format and add version token.

Open
#63,455 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the issue discussion and the two attached files, marshal.patch and marshal2.patch, then inspect the current marshal implementation and its tests. Done means reaching agreement on the format optimization and version-token design, implementing the accepted approach, and verifying compatibility with the relevant test suite.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 19256
Nosy @rhettinger, @jcea, @pitrou, @kristjanvalur, @vstinner, @serhiy-storchaka
Files
  • marshal.patch
  • marshal2.patch
    		•

    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 2013-10-13.22:30:08.540>
labels = ['type-feature']
title = 'Optimize marshal format and add version token.'
updated_at = <Date 2015-01-30.07:21:10.408>
user = 'https://github.com/kristjanvalur'

    bugs.python.org fields:

    activity = <Date 2015-01-30.07:21:10.408>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2013-10-13.22:30:08.540>
creator = 'kristjan.jonsson'
dependencies = []
files = ['32102', '32115']
hgrepos = []
issue_num = 19256
keywords = ['patch']
message_count = 19.0
messages = ['199818', '199819', '199820', '199821', '199822', '199823', '199846', '199850', '199856', '199867', '199869', '199873', '199874', '199878', '199879', '199880', '199882', '199885', '235027']
nosy_count = 6.0
nosy_names = ['rhettinger', 'jcea', 'pitrou', 'kristjan.jonsson', 'vstinner', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19256'
versions = ['Python 3.4']

    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.