[issue4415] Failure to check return value of PyBool_FromLong for NULL

2008-11-24 Thread Brian Szuter 

New submission from Brian Szuter [EMAIL PROTECTED]:

/home/rxc92/project/Python-2.5.2/Python/import.c(imp_is_frozen)
Line 2740

Failed to check that the return value of PyBool_FromLong is not NULL

Referenced:
http://www.python.org/doc/2.5.2/api/boolObjects.html#l2h-400

--
components: None
messages: 76376
nosy: CWRU_Researcher1
severity: normal
status: open
title: Failure to check return value of PyBool_FromLong for NULL
type: resource usage
versions: Python 2.5.3

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4415
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4415] Failure to check return value of PyBool_FromLong for NULL

2008-11-24 Thread Benjamin Peterson 

Benjamin Peterson [EMAIL PROTECTED] added the comment:

There doesn't need to be a NULL check here. The exception is merely
propagated to the caller.

--
nosy: +benjamin.peterson
resolution:  - invalid
status: open - closed

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4415
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com