PyObject_CallObject is not checked for NULL return value · Issue #48668 · python/cpython · GitHub
Skip to content

PyObject_CallObject is not checked for NULL return value #48668

Description

@CWRUResearcher1
BPO 4418
Nosy @benjaminp

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 2008-11-25.02:46:39.445>
created_at = <Date 2008-11-25.01:17:26.869>
labels = ['invalid', 'performance']
title = 'PyObject_CallObject is not checked for NULL return value'
updated_at = <Date 2008-11-25.02:46:39.444>
user = 'https://bugs.python.org/CWRUResearcher1'

bugs.python.org fields:

activity = <Date 2008-11-25.02:46:39.444>
actor = 'benjamin.peterson'
assignee = 'none'
closed = True
closed_date = <Date 2008-11-25.02:46:39.445>
closer = 'benjamin.peterson'
components = []
creation = <Date 2008-11-25.01:17:26.869>
creator = 'CWRU_Researcher1'
dependencies = []
files = []
hgrepos = []
issue_num = 4418
keywords = []
message_count = 3.0
messages = ['76380', '76381', '76391']
nosy_count = 2.0
nosy_names = ['benjamin.peterson', 'CWRU_Researcher1']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue4418'
versions = ['Python 2.5.3']

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    performancePerformance or resource usage

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions