bitwise ops for bytes of equal length

Open
#63,450 53 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
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the linked bitwise_bytes.diff patch and the issue discussion, since no repository file or test is identified. Clarify the intended semantics and scope for bitwise operations on equal-length bytes; done means the agreed behavior is implemented and covered by appropriate tests.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 19251
Nosy @birkenfeld, @rhettinger, @terryjreedy, @gpshead, @ncoghlan, @pitrou, @scoder, @vstinner, @tiran, @cameron-simpson, @socketpair, @vadmium, @serhiy-storchaka, @MojoVampire, @DaGuich
Files
  • bitwise_bytes.diff: 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.20:07:27.218>
labels = ['interpreter-core', 'type-feature', '3.8']
title = 'bitwise ops for bytes of equal length'
updated_at = <Date 2018-05-23.08:37:30.202>
user = 'https://github.com/tiran'

    bugs.python.org fields:

    activity = <Date 2018-05-23.08:37:30.202>
actor = 'MGilch'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-10-13.20:07:27.218>
creator = 'christian.heimes'
dependencies = []
files = ['41569']
hgrepos = []
issue_num = 19251
keywords = ['patch']
message_count = 52.0
messages = ['199785', '199786', '199787', '199792', '199794', '199801', '199802', '199805', '199835', '200330', '200359', '200401', '200696', '200735', '200739', '200740', '202120', '257727', '257728', '257729', '257730', '257748', '257754', '257755', '257761', '257765', '257911', '257914', '257964', '260470', '264184', '264187', '264188', '264190', '264192', '264323', '264324', '264325', '265560', '265561', '316938', '316939', '316940', '316941', '316956', '316957', '317038', '317040', '317095', '317107', '317109', '317116']
nosy_count = 18.0
nosy_names = ['georg.brandl', 'rhettinger', 'terry.reedy', 'gregory.p.smith', 'ncoghlan', 'pitrou', 'scoder', 'vstinner', 'christian.heimes', 'cameron', 'socketpair', 'Ramchandra Apte', 'martin.panter', 'serhiy.storchaka', 'abarnert', 'josh.r', 'cowlicks', 'MGilch']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19251'
versions = ['Python 3.8']

    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.