Re: Negative array indicies and slice()

Date	2012-11-01 13:55 -0700
From	Ethan Furman <ethan@stoneleaf.us>
Subject	Re: Negative array indicies and slice()
References	(3 earlier) <CALwzid=_1TCQC5JryemVfVpBLWq=qZwy4hRjCPA5ha0vSm3=VA@mail.gmail.com> <50918716.3080305@r3dsolutions.com> <5092833F.4070609@stoneleaf.us> <50925DE6.7020100@r3dsolutions.com> <CALwzidkf6yaPz3C9qUtsUe-a+ojmpJNY0FxhBiykZmm6VssYTQ@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.3164.1351803670.27098.python-list@python.org> (permalink)

Show all headers | View raw

Ian Kelly wrote:
> On Thu, Nov 1, 2012 at 5:32 AM, Andrew Robinson wrote:
>> Don't bother to fix the bug; allow Python to crash with a subtle bug that often take weeks to track down by the very small minority doing strange things (Equivalent to the "monkey patch" syndrome of D'Aprano; BTW: The longer the bug is left unfixed, the more people will invent "uses" for it )
> 
> It's been 6 years already.  AFAIK nobody has invented any uses that
> are actually at risk of invoking the GC bug.

The bug is not that slice allows non-numbers, but that slice objects aren't tracked by gc; I'm not 
seeing an issue with not fixing the bug.

~Ethan~

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Negative array indicies and slice() Ethan Furman <ethan@stoneleaf.us> - 2012-11-01 13:55 -0700

csiph-web