bitwise ops for bytes of equal length

Ouverte
#63,450 53 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python
Domaine
compilers

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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']
    

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.