error checking after PyXXX_New

[birkenfeld]

BPO	1445505
Nosy	@Yhg1s, @birkenfeld
Files	PyXXX_New_errorchecking.diff

^{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/Yhg1s'
closed_at = <Date 2006-03-17.19:05:52.000>
created_at = <Date 2006-03-08.09:47:41.000>
labels = ['interpreter-core']
title = 'error checking after PyXXX_New'
updated_at = <Date 2006-03-17.19:05:52.000>
user = 'https://github.com/birkenfeld'

bugs.python.org fields:

activity = <Date 2006-03-17.19:05:52.000>
actor = 'georg.brandl'
assignee = 'twouters'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2006-03-08.09:47:41.000>
creator = 'georg.brandl'
dependencies = []
files = ['7058']
hgrepos = []
issue_num = 1445505
keywords = ['patch']
message_count = 2.0
messages = ['49687', '49688']
nosy_count = 2.0
nosy_names = ['twouters', 'georg.brandl']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1445505'
versions = []

[birkenfeld]

This patch adds a great couple of NULL checks after
PyList_New, PyTuple_New and PyDict_New.

Thomas, can you review that I didn't make an obvious
mistake?

[birkenfeld]

Logged In: YES
user_id=849994

Checked in as rev. 43124, backported most as rev. 43125.