Skip to content

Python should invalidate all non-owned 'thread.lock' objects when forking #57987

Description

@lesha
mannequin
BPO 13778
Superseder
  • bpo-6721: Locks in the standard library should be sanitized on fork
  • 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 = <Date 2012-01-13.10:42:12.861>
    created_at = <Date 2012-01-13.09:24:57.682>
    labels = ['type-feature', 'library']
    title = "Python should invalidate all non-owned 'thread.lock' objects when forking"
    updated_at = <Date 2012-01-13.10:42:12.860>
    user = 'https://bugs.python.org/lesha'

    bugs.python.org fields:

    activity = <Date 2012-01-13.10:42:12.860>
    actor = 'neologix'
    assignee = 'none'
    closed = True
    closed_date = <Date 2012-01-13.10:42:12.861>
    closer = 'neologix'
    components = ['Library (Lib)']
    creation = <Date 2012-01-13.09:24:57.682>
    creator = 'lesha'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 13778
    keywords = []
    message_count = 2.0
    messages = ['151165', '151166']
    nosy_count = 1.0
    nosy_names = ['lesha']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '6721'
    type = 'enhancement'
    url = 'https://bugs.python.org/issue13778'
    versions = ['Python 2.6', 'Python 2.7']

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      stdlibStandard Library Python modules in the Lib/ directorytype-featureA feature request or enhancement

      Projects

      No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions