Negative array indicies and slice()
rosuav at gmail.com
Tue Oct 30 23:00:56 CET 2012
On Wed, Oct 31, 2012 at 8:47 AM, Ian Kelly <ian.g.kelly at gmail.com> wrote:
> On Tue, Oct 30, 2012 at 3:33 PM, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
>> On 30/10/2012 18:02, Ian Kelly wrote:
>>> On Tue, Oct 30, 2012 at 10:14 AM, Ethan Furman <ethan at stoneleaf.us> wrote:
>>>> File a bug report?
>>> Looks like it's already been wontfixed back in 2006:
>> Absolutely bloody typical, turned down because of an idiot. Who the hell is
>> Tim Peters anyway? :)
> I don't really disagree with him, anyway. It is a rather obscure bug
> -- is it worth increasing the memory footprint of slice objects by 80%
> in order to fix it?
Bug report: If I take this gun, aim it at my foot, and pull the
trigger, sometimes a hole appears in my foot.
This is hardly normal use of slice objects. And the penalty isn't a
serious one unless you're creating cycles repeatedly.
More information about the Python-list