[issue4461] parameters of PyLong_FromString() are not checked for NULL

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Merged. Thanks for the report, Brian. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue4461] parameters of PyLong_FromString() are not checked for NULL

Changes by Mark Dickinson <[EMAIL PROTECTED]>: -- versions: -Python 2.6, Python 2.7 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyth

[issue4461] parameters of PyLong_FromString() are not checked for NULL

Mark Dickinson <[EMAIL PROTECTED]> added the comment: All tests pass with this patch. Committed to trunk, r67590. Will merge to 2.7, 3.0 and 3.1. ___ Python tracker <[EMAIL PROTECTED]> __

[issue4461] parameters of PyLong_FromString() are not checked for NULL

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Patch looks fine. (!) Okay just to apply this to 2.6 and up? It's not a bugfix. -- versions: -Python 2.5.3 ___ Python tracker <[EMAIL PROTECTED]> __

[issue4461] parameters of PyLong_FromString() are not checked for NULL

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: This is an internal call, so am not worried about "const char *s" being NULL -- that duty belongs to the caller who creates the pointer in the first place. That being said, it wouldn't hurt to add an assertion at the beginning of the funct

[issue4461] parameters of PyLong_FromString() are not checked for NULL

New submission from Brian Szuter <[EMAIL PROTECTED]>: Python-2.5.2/Python/ast.c(parsenumber) Line 3061 The parameters of PyLong_FromString() are not checked for NULL before the method is called. -- components: None messages: 76602 nosy: CWRU_Researcher1 severity: normal status: open tit