Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <2f026694-0905-49f8-bcae-7e4d55df5d49@z22g2000prd.googlegroups.com>
References: <Xns9F9684761E3AOKB@88.198.244.100> <436fb6a3-1075-45a6-8f93-5612d050b11a@q35g2000prh.googlegroups.com> <CAPTjJmqESQc2HrMNSKLbnG5C8fvrOQvaPme0vTN9VS9eQkndFg@mail.gmail.com> <mailman.2558.1320799508.27778.python-list@python.org> <4eb9e9c2$0$29988$c3e8da3$5496439d@news.astraweb.com> <mailman.2577.1320879720.27778.python-list@python.org> <4ebb08b6$0$29970$c3e8da3$5496439d@news.astraweb.com> <mailman.2580.1320888461.27778.python-list@python.org> <2f026694-0905-49f8-bcae-7e4d55df5d49@z22g2000prd.googlegroups.com>
From: Devin Jeanpierre <jeanpierreda@gmail.com>
Date: Wed, 9 Nov 2011 23:40:25 -0500
Subject: Re: all() is slow?
To: alex23 <wuwei23@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2585.1320900069.27778.python-list@python.org>
Lines: 71
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:15527

> (And it's really not a good idea to be proud of your
> ignorance...)

I wasn't bragging.

> But you're happy to accept the opinions of random posters saying "exec
> is evil"?
[...]
> As opposed to your in-depth critique?
[...]
> No, instead you have a thread full of people happy to criticise
> something for which they're providing no alternative implementation.
> You can't exactly say _why_ it's bad, other than other people have
> echoed it, but you won't actually do anything about it.

I said it was bad because I found it difficult to read and it was
"weird". I also mentioned that it's conceivable that it has security
flaws, but that's not as big a deal. I believe I also said that it was
bad because it resulted in """arbitrary""" limitations in
functionality. So, yes, I did say why it's bad, and it's not just
because other people say so. My reasons are weak, but that's a
different story.

I also mentioned the alternative implementation, which uses a dict.
There was even already a patch submitted to make namedtuple work this
way, so I don't think I had to be too specific. R. Hettinger rejected
this patch, which was what I was referring to when I was referring to
handwaviness.

So, no.

> Just as I thought.

Woo condescension.

Devin

On Wed, Nov 9, 2011 at 10:50 PM, alex23 <wuwei23@gmail.com> wrote:
> On Nov 10, 11:26=C2=A0am, Devin Jeanpierre <jeanpierr...@gmail.com> wrote=
:
>> I don't really know anything about him or why people respect him, so I
>> have no reason to share your faith.
>
> But you're happy to accept the opinions of random posters saying "exec
> is evil"? (And it's really not a good idea to be proud of your
> ignorance...)
>
>> Like, why can't "--" be a name?
>
> Why would you ever want it to be?
>
>> I don't like the use of exec, and I don't like the justification (it
>> seems handwavy).
>
> As opposed to your in-depth critique?
>
>> I pointed this out in a thread full of people saying
>> "never EVER use exec this way", so it's obviously not just me that
>> thinks this is awful.
>
> No, instead you have a thread full of people happy to criticise
> something for which they're providing no alternative implementation.
> You can't exactly say _why_ it's bad, other than other people have
> echoed it, but you won't actually do anything about it.
>
>> I think somebody will read it and think this is a good idea.
>
> Just as I thought.
> --
> http://mail.python.org/mailman/listinfo/python-list
>