On 6/19/07, Chris McDonough <[EMAIL PROTECTED]> wrote:
> Given that security is a concern at all, the only truly reasonable
> way to "limit security issues" is to disallow item and attribute
> access completely within the string templating expression syntax. It
> seems gratuituous to me to encoura
On 3/5/07, Ka-Ping Yee <[EMAIL PROTECTED]> wrote:
> On Tue, 6 Mar 2007, Neil Schemenauer wrote:
> > We don't suggest that file-like objects
> > should implement __read__() instead of read(), for example.
>
> There is a convention and it is applied quite consistently:
>
> Double-underscores are
On 1/16/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> I know Guido is against attribute syntax for dict.items and friends,
> and I agree with him for reasons I can't quite put my finger on.
I agree that making dict.items and friends into attributes feels
wrong. I suspect it may be useful to put a
Some very good points made here.
On 1/10/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> Yeah, I like reusing the variable names bound in a for loop. And unless
> we are going to attempt to simplify the in...
>
> for in ...:
> ...
>
> to only be a bare name, and not things like 'i,
On 1/10/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> According to the translation rules Colin has previously provided...
>
> re = get_resource()
> ...
> try:
> something()
> except RareException as re:
> ...
> ...
> re.use_resource()
>
> is translated into
Well, now I have to delurk.
I've been watching with growing excitement. Between the changes to
the scope rules for list comprehensions, and this change for except
blocks, I wondered if Python might have been moving in the direction
of block scoped variables where appropriate as a philosophy.
I a
