Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #32571 > unrolled thread

Re: Negative array indicies and slice()

Started byEthan Furman <ethan@stoneleaf.us>
First post2012-11-01 13:55 -0700
Last post2012-11-01 13:55 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#32571 — Re: Negative array indicies and slice()

FromEthan Furman <ethan@stoneleaf.us>
Date2012-11-01 13:55 -0700
SubjectRe: Negative array indicies and slice()
Message-ID<mailman.3164.1351803670.27098.python-list@python.org>
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~

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web