[Python-bugs-list] [ python-Bugs-493936 ] _PyEval_SliceIndex vs NULL

[noreply@sourceforge.net]

Bugs item #493936, was opened at 2001-12-16 10:57
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=493936&group_id=5470

Category: Python Interpreter Core
>Group: Not a Bug
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Tim Peters (tim_one)
Assigned to: Tim Peters (tim_one)
Summary: _PyEval_SliceIndex vs NULL

Initial Comment:
_PyEval_SliceIndex goes out of its way to say 
everything's fine when passed a NULL pointer, but 
leaves the output *pi untouched in that case.  But, 
AFAICT, it doesn't make sense to call this routine 
with a NULL pointer, and nobody does.  So it should 
assert that v is not NULL.  Hold for 2.3 "just in 
case".

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-12-16 11:45

Message:
Logged In: YES 
user_id=31435

Thanks!  I checked in your comment as a code comment, since 
it's mondo obscure even after a 10-second nap <wink>.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-16 11:33

Message:
Logged In: YES 
user_id=6380

Get some sleep. :-)

_PyEval_SliceIndex() is called by apply_slice() which can be
called by the SLICE opcode with v and/or w equal to NULL.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=493936&group_id=5470