On Feb 22, 2008, at 2:25 AM, Guido van Rossum wrote:
> What syntax would you allow instead? Just del variable, variable, ...?
Yes. These are and should be legal
del a, b[1], c.d
del (e+f).g[9]().h
but I think this should not be legal
del a, (b, c)
That should raise
SyntaxError: can't dele
What syntax would you allow instead? Just del variable, variable, ...?
On Wed, Feb 20, 2008 at 12:45 PM, Andrew Dalke
<[EMAIL PROTECTED]> wrote:
> For lack of a better term, I'll call this a destructuring del
>
> del (a, (b, (c)))
>
> I propose that it should not be valid in Python 3.
>
> It
For lack of a better term, I'll call this a destructuring del
del (a, (b, (c)))
I propose that it should not be valid in Python 3.
It's supported in 2.x and 3.0a2. It's never caused anyone problems.
No one (that I can find through 10 minutes of grepping) uses it.
When I figured out th
On Sat, 16 Feb 2008 16:32:43 +, Giovanni Bajo wrote:
>> At the very least, can you add the issue to the tracker so we'll have a
>> permanent reminder until it's resolved?
>
> Done: issue 2128.
The patch was uploaded a few days ago. Can any Windows maintainer find
some time to review it?
T
2008/2/21, Aahz <[EMAIL PROTECTED]>:
> >From my POV, this is cruft in the builtins (I mostly do web apps) -- and
> I don't particularly like your suggestions for modifying the result of
> breakpoint() (note that Facundo wants to use gdb). Why not simply
No, no, my mistake, I also use pdb.
On Thu, Feb 21, 2008, Barry Warsaw wrote:
>
> So I have some particularly troublesome code that I want to set a
> breakpoint at and start stepping through. I usually will stick this
> tidbit at the place I want to break:
>
> good_code()
> import pdb; pdb.set_trace()
> call_bug
2008/2/21, Barry Warsaw <[EMAIL PROTECTED]>:
> good_code()
> import pdb; pdb.set_trace()
> call_buggy_code()
>
> ...
>
> good_code()
> breakpoint()
> call_buggy_code()
"import gdb;gdb.set_trace()" is my second-most-used debugging tool
(the first one is "print"), so
On Thu, 21 Feb 2008 10:01:56 -0500, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>I know this will get shot down like a Navy missile aimed at an errant
>spy satellite, but I'm going to suggest it anyway.
>
>Several of us have been talking about merging t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know this will get shot down like a Navy missile aimed at an errant
spy satellite, but I'm going to suggest it anyway.
Several of us have been talking about merging the two Emacs Python
modes and this prompted a discussion of Ken Manheimer's exc
