Skip to content

Measure if _warnings.c is still worth having #69126

@brettcannon

Description

@brettcannon
BPO 24938
Nosy @brettcannon
Files
  • issue24938.diff: Hack to create _frozen_warnings
  • 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 = 'https://github.com/brettcannon'
    closed_at = <Date 2015-09-06.18:42:28.459>
    created_at = <Date 2015-08-25.18:49:27.517>
    labels = ['performance']
    title = 'Measure if _warnings.c is still worth having'
    updated_at = <Date 2015-09-06.18:42:28.457>
    user = 'https://github.com/brettcannon'

    bugs.python.org fields:

    activity = <Date 2015-09-06.18:42:28.457>
    actor = 'brett.cannon'
    assignee = 'brett.cannon'
    closed = True
    closed_date = <Date 2015-09-06.18:42:28.459>
    closer = 'brett.cannon'
    components = []
    creation = <Date 2015-08-25.18:49:27.517>
    creator = 'brett.cannon'
    dependencies = []
    files = ['40269']
    hgrepos = []
    issue_num = 24938
    keywords = ['patch']
    message_count = 4.0
    messages = ['249150', '249152', '249213', '250004']
    nosy_count = 1.0
    nosy_names = ['brett.cannon']
    pr_nums = []
    priority = 'low'
    resolution = 'works for me'
    stage = 'needs patch'
    status = 'closed'
    superseder = None
    type = 'performance'
    url = 'https://bugs.python.org/issue24938'
    versions = ['Python 3.6']

    Metadata

    Metadata

    Assignees

    Labels

    performancePerformance or resource usage
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions