"Brendan Miller" wrote:
>
>Yes, I also recently noticed the bug in python's parser that doesn't
>let it handle squigly braces and the bug in the lexer that makes white
>space significant. I'm surprised the dev's haven't noticed this yet.
It's very dangerous to make a post like this without includ
Yes, I also recently noticed the bug in python's parser that doesn't
let it handle squigly braces and the bug in the lexer that makes white
space significant. I'm surprised the dev's haven't noticed this yet.
On Sat, Jan 17, 2009 at 2:09 AM, v4vijayakumar
wrote:
> I saw some code where someone is
Roy Smith wrote:
In article ,
Steve Holden wrote:
Roy Smith wrote:
In article
<6264e675-ddd4-446a-822a-cc82e8f87...@w1g2000prk.googlegroups.com>,
v4vijayakumar wrote:
I saw some code where someone is really managed to import braces from
__future__. ;)
def test():
#{
print "hell
In article ,
Steve Holden wrote:
> Roy Smith wrote:
> > In article
> > <6264e675-ddd4-446a-822a-cc82e8f87...@w1g2000prk.googlegroups.com>,
> > v4vijayakumar wrote:
> >
> >> I saw some code where someone is really managed to import braces from
> >> __future__. ;)
> >>
> >> def test():
> >> #{
Roy Smith wrote:
> In article
> <6264e675-ddd4-446a-822a-cc82e8f87...@w1g2000prk.googlegroups.com>,
> v4vijayakumar wrote:
>
>> I saw some code where someone is really managed to import braces from
>> __future__. ;)
>>
>> def test():
>> #{
>> print "hello"
>> #}
>
> That usage is obsolete
In article
<6264e675-ddd4-446a-822a-cc82e8f87...@w1g2000prk.googlegroups.com>,
v4vijayakumar wrote:
> I saw some code where someone is really managed to import braces from
> __future__. ;)
>
> def test():
> #{
> print "hello"
> #}
That usage is obsolete. Current best practice is:
def
