Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

assertion failure in _warnings.warn() in case of a bad __name__ global #75747

Closed
orenmn mannequin opened this issue Sep 24, 2017 · 3 comments
Closed

assertion failure in _warnings.warn() in case of a bad __name__ global #75747

orenmn mannequin opened this issue Sep 24, 2017 · 3 comments
Labels
3.7 only security fixes extension-modules C modules in the Modules dir type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@orenmn
Copy link
Mannequin

orenmn mannequin commented Sep 24, 2017

BPO 31566
Nosy @serhiy-storchaka, @orenmn
PRs
  • bpo-31566: Fix an assertion failure in _warnings.warn() in case of a bad __name__ global #3717
  • [3.6] bpo-31566: Fix an assertion failure in _warnings.warn() in case of a bad __name__ global. (GH-3717) #3730
  • 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 2017-09-27.05:01:23.965>
    created_at = <Date 2017-09-24.06:53:40.936>
    labels = ['extension-modules', '3.7', 'type-crash']
    title = 'assertion failure in _warnings.warn() in case of a bad __name__ global'
    updated_at = <Date 2017-09-27.05:01:23.963>
    user = 'https://github.com/orenmn'

    bugs.python.org fields:

    activity = <Date 2017-09-27.05:01:23.963>
    actor = 'serhiy.storchaka'
    assignee = 'none'
    closed = True
    closed_date = <Date 2017-09-27.05:01:23.965>
    closer = 'serhiy.storchaka'
    components = ['Extension Modules']
    creation = <Date 2017-09-24.06:53:40.936>
    creator = 'Oren Milman'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 31566
    keywords = ['patch']
    message_count = 3.0
    messages = ['302829', '302877', '302885']
    nosy_count = 2.0
    nosy_names = ['serhiy.storchaka', 'Oren Milman']
    pr_nums = ['3717', '3730']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'crash'
    url = 'https://bugs.python.org/issue31566'
    versions = ['Python 3.6', 'Python 3.7']

    @orenmn
    Copy link
    Mannequin Author

    orenmn mannequin commented Sep 24, 2017

    The following code causes an assertion failure:
    __name__ = b'foo'
    __file__ = None
    import _warnings
    _warnings.warn('bar')

    This is because setup_context() (in Python/_warnings.c) assumes that __name__
    is a string, and so it passes it to _PyUnicode_EqualToASCIIString(), which
    asserts it is a string.

    @orenmn orenmn mannequin added 3.7 only security fixes extension-modules C modules in the Modules dir type-crash A hard crash of the interpreter, possibly with a core dump labels Sep 24, 2017
    @serhiy-storchaka
    Copy link
    Member

    New changeset 5d3e800 by Serhiy Storchaka (Oren Milman) in branch 'master':
    bpo-31566: Fix an assertion failure in _warnings.warn() in case of a bad __name__ global. (bpo-3717)
    5d3e800

    @serhiy-storchaka
    Copy link
    Member

    New changeset 415cc1f by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6':
    [3.6] bpo-31566: Fix an assertion failure in _warnings.warn() in case of a bad __name__ global. (GH-3717) (bpo-3730)
    415cc1f

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    3.7 only security fixes extension-modules C modules in the Modules dir type-crash A hard crash of the interpreter, possibly with a core dump
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant